| Summary: | Support comments for Enum Literals | ||
|---|---|---|---|
| Product: | [Modeling] EMF | Reporter: | Miles Parker <milesparker> |
| Component: | Core | Assignee: | Ed Merks <Ed.Merks> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Miles Parker
Enum literals aren't properties. They do have translatable labels. I'm not sure who would generally use this. This is actually a pretty common case for when you want to support self documenting models. (Yes, some of us do like to document our models. :P) Without this feature there is no way in the model to provide a description for what a given literal actually signifies. You can provide model documentation via Ecore annotations. They'll show up in the Javadoc and you can access them programmatically with org.eclipse.emf.ecore.util.EcoreUtil.getDocumentation(EModelElement) |