Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-ui-dev] Extension point evolvement question

I don't know of such a document. If there was one, then it would be very short: Don't break existing clients.

If you add new attributes or elements, the documentation should include "since x.y", the element/attribute should be optional, and the code that processes the contributions needs to work when the element/attribute is not there.

HTH
Markus



From:        Lars Vogel <lars.vogel@xxxxxxxxxxx>
To:        "Eclipse Platform UI component developers list." <platform-ui-dev@xxxxxxxxxxx>
Date:        2016-10-04 17:45
Subject:        [platform-ui-dev] Extension point evolvement question
Sent by:        platform-ui-dev-bounces@xxxxxxxxxxx




Friends of Platform UI,

do we have a wiki / guideline for evolving extension points? I think
adding a new attribute to an existing extension point is save but have
not found a wiki reference for that.

I want to enable dependency injection in e3 parts and to allow views
to opt in, I want to introduce a new flag in the view extension point
schema. See Bug 500688.

Best regards, Lars

--
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vogel@xxxxxxxxxxx, Web:
http://www.vogella.com
_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev



Back to the top