In many cases, the list of choices that the default ContentAssist provides is too many. The context may limit the possibilities. For example, the composition elements in a Logical or Platform Entity can only realize the elements of the Conceptual or Logical Entity that is realized as a whole (this code is already in UddlProposalProvider) . Other examples are that some lists should never include duplicates - so the list of choices should never include things already in the list.
This task is about improving com.epistimis.uddl.ui.contentassist.UddlProposalProvider to address other places where we can limit available choices - because that makes the tool less cluttered/ easier to use.
Documentation:
https://www.eclipse.org/Xtext/documentation/310_eclipse_support.html#content-assist
In many cases, the list of choices that the default ContentAssist provides is too many. The context may limit the possibilities. For example, the composition elements in a Logical or Platform Entity can only realize the elements of the Conceptual or Logical Entity that is realized as a whole (this code is already in
UddlProposalProvider) . Other examples are that some lists should never include duplicates - so the list of choices should never include things already in the list.This task is about improving
com.epistimis.uddl.ui.contentassist.UddlProposalProviderto address other places where we can limit available choices - because that makes the tool less cluttered/ easier to use.Documentation:
https://www.eclipse.org/Xtext/documentation/310_eclipse_support.html#content-assist