eclipse-xtext / eclipse-xtext/xtext
Better Control of new Generator
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 831
- Forks
- 330
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 12
Description
it would be nice if it would be more easy to control what the new workflow does and what not regarding enablement / disablement of fragments / implicit stuff.
having to subclass to get rid of a fragment is really painful
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names the new Generator workflow but no files or tests. Start by locating that generator and its fragment enablement and implicit-configuration paths; done means callers can control those choices without subclassing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100