We currently have a manually implemented class org.bumble.eatxt.ui.contentassist.EatxtProposalProvider which produces code completion suggestions when entering names of new instances. There is one completion method for each meta-model element. The code is almost identical for each meta-model element and could easily be auto-generated. That would improve our ability to adapt to new meta-model versions.
The easiest way is probably to create a new fragment based on the existing one. We can override it and include it in the MWE2 workflow, similar to what we did for the formatter.
We currently have a manually implemented class
org.bumble.eatxt.ui.contentassist.EatxtProposalProviderwhich produces code completion suggestions when entering names of new instances. There is one completion method for each meta-model element. The code is almost identical for each meta-model element and could easily be auto-generated. That would improve our ability to adapt to new meta-model versions.The easiest way is probably to create a new fragment based on the existing one. We can override it and include it in the MWE2 workflow, similar to what we did for the formatter.