MPS-extensions
MPS-extensions copied to clipboard
Use of grammar cells forces creation of dummy component to handle dependency problem
Using MPS 2020.3 and grammar cells. This is discussed in Slack, https://jetbrains-mps.slack.com/archives/C3YUV3YK0/p1628146601046300. A a (new) user, this seems to expose quite some details as to how grammar cells are implemented and require a workaround at the language definition level. I don't, at this time, have any suggestions as to how to address but thought I would enter it as an issue.
I can't access the original Slack thread. @slisson can you explain in 2 sentences what the original problem was? How can the issue without adding the dummy component be reproduced? If the editor language needs to be involved, it could be added as a language engaged on generation in the quick fix instead of creating the dummy node.
If I remember correctly, it's related to how MPS searches for languages extending the editor of a specific concept and the fact that grammar cells generates those extensions and they are not part of the original model.