Skip to content

Add not yet explicitly implemented EMF flags for references and/or attributes #31

@Noah1891

Description

@Noah1891

Besides the already implemented "derived" containers, EMF has multiple other flags that can be set when defining a metamodel. Right now all containers implicitly use the default values of "unique", "ordered" and "changeable", while "volatile" and "transient" are implicitly true for "derived" containers which represents the standard behaviour as well. All those mentioned and additional flags and their meaning are listed in this uploaded file:

EMFReferenceTypes.md

It has to be decided which of those should be explicitly implemented for EMFular.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions