Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide better implementation for Metamodel #16

Open
arcanefoam opened this issue Nov 2, 2017 · 0 comments
Open

Provide better implementation for Metamodel #16

arcanefoam opened this issue Nov 2, 2017 · 0 comments

Comments

@arcanefoam
Copy link
Member

Given that we want to avoid a dependency on EMF, the implementation of the Trace metamodel should be a bit more robust and, at least, correctly handle opposite properties.
The idea is to use an inner class to represent a StructuralFeature, attributes are still represented as fields.
The inner class provides methods to create/destroy relations between elements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant