Community
Participate
Working Groups
Build Identifier: 20110916-0149 When a fragment of a qualified name consists in a keyword, or the concrete syntax defines a different delimiter, the rules ValueConverter for qualified names transforms to the proper internal String representation. The quick-fix provider for linker errors pushes this internal String representation to the document instead of transforming it via the ValueConverter. So Caret chars were not added and delimiter were not replaced. In my project I have developed a generic bug fix by overwriting DefaultQuickfixProvider.createLinkingIssueResolutions. It is not trivial because some interfaces had to be changed. If you are interested I can provide the fix. Reproducible: Always Steps to Reproduce: 1. define a object that has keywords in its qualified name 2. define a cross reference using this name 3. modify the cross reference so a linker error appears 4. select a quick-fix proposal with that mane ==> the internal representation will be added to the document
Created attachment 205596 [details] override DefaultQuickfixProvider.createLinkingIssueResolutions to solve the bug
we have to deal with keywords as cross reference terminal and ignore case linking, too.
Pushed to master.
Closing all bugs that were set to RESOLVED before Neon.0