You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have verified that I am running the latest version of the EcoreNetto
I have searched open and closed issues to ensure it has not already been reported
Description
Summary: Cross-reference handling relies on string manipulation and hardcoded assumptions: the .ecore extension is hardcoded, %20 is the only URL escape decoded, and implicit #// references are rewritten by string concatenation. This is brittle for paths with other escaped characters or different extensions.
Proposed solution: Use Uri/Uri.UnescapeDataString for path decoding and proper URI fragment handling instead of ad-hoc string ops; avoid hardcoding the file extension where possible.
Prerequisites
Description
.ecoreextension is hardcoded,%20is the only URL escape decoded, and implicit#//references are rewritten by string concatenation. This is brittle for paths with other escaped characters or different extensions.ECoreNetto/ModelElement/EObject.cs:392-416(ProcessAttributeValue),ECoreNetto/ECoreParser.cs:85(Replace("%20", " ")),ECoreNetto/Resource/Resource.cs:255(.ecorecheck),ECoreNetto/ModelElement/NamedElement/EPackage.cs:212Uri/Uri.UnescapeDataStringfor path decoding and proper URI fragment handling instead of ad-hoc string ops; avoid hardcoding the file extension where possible.%20load correctly.