-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Managed Build Definitions extension point should prefer "identifier" type of attribute #592
Comments
…e of attribute Add meta information for id-like attributes Signed-off-by: Alexander Fedorov <alexander.fedorov@arsysop.ru>
Add meta information for id-like attributes Signed-off-by: Alexander Fedorov <alexander.fedorov@arsysop.ru>
…ier" type of attribute" This reverts commit 7136606.
…f attribute" This reverts commit 7136606.
Yes, it is easy to implement this for top-level entries, but we have a lot of others, like ToolChain inside Configuration. So, it seems that I need to introduce id metadata not "by schema", but rather "by entity", to check result after each minor step. |
I'm afraid this is not possible to implement as identifiers may come from dynamic extension and we cannot determine the whole list of possible identifiers in PDE static context. |
Describe the bug
Currently fields like
superClass
has typestring
and this is not helpful to specify the right valueTo Reproduce
Steps to reproduce the behavior:
Expected behavior
Fields that expect identifiers suggest them from the list of existing values
The text was updated successfully, but these errors were encountered: