Community
Participate
Working Groups
Build Identifier: 20110916-0149 Just a minor enhancement. The factory org.eclipse.xtext.naming.QualifiedName.create(String...) checks that you cannot create a qualified name with a "null" segment. However, the org.eclipse.xtext.naming.QualifiedName.append(String) function does not. Would be better to always guarantee the non-null invariant and also check the parameter of the append operation. Reproducible: Always
fixed; pushed to 'master'.
We have to make sure that no client code in the frameworks passes null to QualifiedName#append
As as discussed internally, I've removed the null-check for now since it might lead to new exceptions in clients. The plan is to apply the apply the null-check again right after we have release Xtext 2.2. This will allow us to do more thorough testing. The commit can be re-applied via "git cherry-pick -x b74a06f705a9a0750289e2152d49941f4727e756"
cherry-picked and pushed.
Requested via bug 522520. -M.