Community
Participate
Working Groups
We should evaluate whether this reduces the necessary complexity for the generator fragments and other parts of the code base.
The idea is to have a URI to any generated EPackages, so that one can refer to generated EPackages, just like to other EPackages in a rest-like manner.
I like the idea to have a .ecore file in the src-gen folder for each EPackage that is derived from the grammar. This way, - one can easily move this file to src when switching from "generate" to "import" - people can open the .ecore file in their favorite .ecore editor to understand how Xtext derives EPackages. When I introduce people to Xtext I usually ask them to do this step.
(In reply to comment #2) > I like the idea to have a .ecore file in the src-gen folder for each EPackage > that is derived from the grammar. Generating a clone of the EPackage isn't a problem. But wouldn't it be even nicer, if one could open the Xtext file with a reflective editor and see (and copy & paste) the EPackage in it?
Not worth the effort.