The default values of the attributes of the Ecore metamodel seem to not be taken into

Ecore metamodel default values not taken into account (e.g. "unique=true") about nmf HOT 2 CLOSED

nmfcode commented on July 24, 2024

Ecore metamodel default values not taken into account (e.g. "unique=true")

from nmf.

Comments (2)

georghinkel commented on July 24, 2024

The generation of default value literals was not working for nullable types. But as Ecore does not define a default value of the lower bound property, attributes like unique or ordered are rendered with type Nullable<bool>. This is now solved with the latest commit 393bce4.

The metamodel you supplied generates the following backing fields for Test1:

        /// <summary>
        /// The backing field for the UniqueOrdered property
        /// </summary>
        private ObservableAssociationOrderedSet<ITest1> _uniqueOrdered;

        /// <summary>
        /// The backing field for the UniqueNonOrdered property
        /// </summary>
        private ObservableAssociationSet<ITest1> _uniqueNonOrdered;

        /// <summary>
        /// The backing field for the NonUniqueOrdered property
        /// </summary>
        private ObservableAssociationList<ITest1> _nonUniqueOrdered;

        /// <summary>
        /// The backing field for the NonUniqueNonOrdered property
        /// </summary>
        private ObservableAssociationList<ITest1> _nonUniqueNonOrdered;

        /// <summary>
        /// The backing field for the Opposite1Unique property
        /// </summary>
        private Test1Opposite1UniqueCollection _opposite1Unique;

        /// <summary>
        /// The backing field for the Opposite2Unique property
        /// </summary>
        private Test1Opposite2UniqueCollection _opposite2Unique;

        private static IClass _classInstance;

You can see that the references are now typed correctly with hash sets or ordered sets.

from nmf.