Summary: | Unhelpful org.eclipse.xtext.util.EmfFormatter list index 'stabilization' | ||
---|---|---|---|
Product: | [Modeling] TMF | Reporter: | Ed Willink <ed> |
Component: | Xtext | Assignee: | Project Inbox <tmf.xtext-inbox> |
Status: | NEW --- | QA Contact: | |
Severity: | minor | ||
Priority: | P3 | CC: | christian.dietrich.opensource, sebastian.zarnekow |
Version: | unspecified | Keywords: | helpwanted |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows 10 | ||
Whiteboard: |
Description
Ed Willink
2019-10-11 07:19:26 EDT
I am not sure if changing this would lead to semantic api changes and thus annoy people but maybe that could be done configurable Obviously any change is a semantic API breakage; it's just a matter of whether it's reasonable or not. For the compare-equals use case, it makes no difference since equality of two serializations is unaffected. There is an issue of equality with a saved EmfFormatter serialization, but I have always avoided that since certainly I never regarded EMFFormatter as stable. I always compare EMFFormatter serializations of a new / old Resource not a new / old EMFFormatter serialization. For the human browsing use case, the change is a fractional improvement, but EmfFormatter is not very good for humans anyway. I find an EMF tree or pure XMI better. If you have other use cases and they are affected, then WONTFIX. If not it's a minor bug fix. I think it wouldn't do any harm to add an option that allows to disable the padding. |