[1990] Fix the EnumerationDefinition compartment name according to specification

Bug: #1990
Signed-off-by: Guillaume Coutable <guillaume.coutable@obeo.fr>

Author: gcoutable

CHANGELOG.adoc

@@ -92,6 +92,7 @@ For example `ViewUsage` elements are no longer rendered in _parts_ compartments.
 - https://github.com/eclipse-syson/syson/issues/2050[#2050] [diagrams] Fix an issue where creating a `PerformActionUsage` from the `ActionUsage` graphical node (or any other graphical node that allows to create it) was displaying it in the diagram background and its compartments every time.
 It now follows the same rule than all other graphical node: if a compartment that can display the new `PerformActionUsage` is displayed, then the new `PerformActionUsage` is displayed in this compartment, otherwise it is displayed in the diagram background.
 - https://github.com/eclipse-syson/syson/issues/2046[#2046] [diagrams] Fix an issue where the creation of a `RequirementUsage` from a `Package` graphical node was not revealing it.
+- https://github.com/eclipse-syson/syson/issues/1990[#1990] [diagrams] Fix the `EnumerationDefinition` graphical node compartment name to follow the SysMLv2 specification.
 
 === Improvements
 

backend/application/syson-application/docker-compose.yml

@@ -13,6 +13,7 @@ services:
     ports:
       - '8080:8080'
     environment:
+      SIRIUS_COMPONENTS_DIAGRAM_DEBUG: true
       SPRING_DATASOURCE_URL: jdbc:postgresql://database/postgres
       SPRING_DATASOURCE_USERNAME: test_username
       SPRING_DATASOURCE_PASSWORD: test_password

backend/application/syson-application/src/test/java/org/eclipse/syson/application/controllers/diagrams/general/view/GVSubNodeStructureCreationTests.java

@@ -127,7 +127,7 @@ private static Stream<Arguments> attributeUsageChildNodeParameters() {
 
     private static Stream<Arguments> enumerationDefinitionChildNodeParameters() {
         return Stream.of(
-                Arguments.of(SysmlPackage.eINSTANCE.getEnumerationUsage(), "enumerations", SysmlPackage.eINSTANCE.getEnumerationDefinition_EnumeratedValue()),
+                Arguments.of(SysmlPackage.eINSTANCE.getEnumerationUsage(), "enums", SysmlPackage.eINSTANCE.getEnumerationDefinition_EnumeratedValue()),
                 Arguments.of(SysmlPackage.eINSTANCE.getDocumentation(), DOC_COMPARTMENT, SysmlPackage.eINSTANCE.getElement_Documentation()))
                 .map(TestNameGenerator::namedArguments);
     }

backend/views/syson-standard-diagrams-view/src/main/java/org/eclipse/syson/standard/diagrams/view/nodes/CompartmentNodeDescriptionProvider.java

@@ -53,6 +53,8 @@ protected String getCustomCompartmentLabel() {
         } else if (this.eReference == SysmlPackage.eINSTANCE.getRequirementUsage_RequiredConstraint() ||
                 this.eReference == SysmlPackage.eINSTANCE.getRequirementDefinition_RequiredConstraint()) {
             customLabel = "require constraints";
+        } else if (this.eReference == SysmlPackage.eINSTANCE.getEnumerationDefinition_EnumeratedValue()) {
+            customLabel = "enums";
         }
         return customLabel;
     }

doc/content/modules/user-manual/pages/release-notes/2026.3.0.adoc

@@ -23,12 +23,13 @@ They can also add their own SysML-based validation rules by returning additional
 
 ** Fix an issue where some type of `Elements` could appear in the wrong compartment if they shared a common type with said compartment, for example `ViewUsage` elements could appear in the _parts_ compartment since they extends `PartUsage`.
 ** Allow redefining a `PartUsage` with the same name as the redefined `Usage`.
-** Fix an issue where `ConnectionDefinition` graphical nodes where incorrectly labelled as `«part def»` instead of `«connection def»`.
+** Fix an issue where `ConnectionDefinition` graphical nodes where incorrectly labeled as `«part def»` instead of `«connection def»`.
 ** Fix an issue where it was possible to create a `SatisfyRequirementUsage` from the `SatisfyRequirementUsage` graphical edge tool with a target that is not a `RequirementUsage`.
 ** Fix an issue where it was not possible to drag and drop a `LibraryPackage` from the _Explorer_ to a diagram.
 ** Fix an issue where creating a `PerformActionUsage` from the `ActionUsage` graphical node (or any other graphical node that allows to create it) was displaying it in the diagram background and its compartments every time.
 It now follows the same rule than all other graphical node: if a compartment that can display the new `PerformActionUsage` is displayed, then the new `PerformActionUsage` is displayed in this compartment, otherwise it is displayed in the diagram background.
 ** Fix an issue where the creation of a `RequirementUsage` from a `Package` graphical node was not revealing it.
+** Fix the `EnumerationDefinition` graphical node compartment name from `enumerations` to `enums`, to follow the SysMLv2 specification.
 
 * In textual import/export:
 
@@ -38,7 +39,8 @@ It now follows the same rule than all other graphical node: if a compartment tha
 ** Fix the textual import to properly resolve the _payload_ argument of a `SendActionUsage` used in a `TransitionUsage`.
 The following model is now properly imported:
 +
-```
+[source]
+----
 package Package1 {
     attribute def Sig ;
     part p;
@@ -53,12 +55,13 @@ package Package1 {
               then s3;
     }
 }
-```
+----
 
 ** Fix the textual import to properly resolve unnamed redefined `Feature` in a `FeatureChain`.
 The following model is now properly imported:
 +
-```
+[source]
+----
 part system {
 	part def Logical {
 		part component {
@@ -70,12 +73,13 @@ part system {
 	}
 	part c2  = l.component.component2; // "component" now resolves to "p1::l::component" instead of "p1::Logical::component"
 }
-```
+----
 
 ** Fix the textual import so `Relationships` can be annotated.
 Such as in :
 
-```
+[source]
+----
 package Test {
     metadata def MyAnnotation;
 
@@ -87,7 +91,7 @@ package Test {
 
    item def MyItem2;
 }
-```
+----
 
 ** Fix a textual export problem while exporting `LiteralString` with no value.
 ** Fix the export of `LiteralString` with backslash characters.
@@ -106,9 +110,10 @@ The previous implementation was importing the value "A \\ B".
 
 ** Improve the computation of _featuringType_ on `Feature` to avoid getting the following validation error:
 +
-```
+[source]
+----
 If a Feature is owned via a FeatureMembership, then it must have a featuringType for which the operation isFeaturingType returns true. (checkFeatureFeatureMembershipTypeFeaturing constraint on Feature is not respected for Test::MyItemDef::myFeature)
-```
+----
 
 == Improvements
 
@@ -148,7 +153,8 @@ Instead, SysON will now use the inherited elements without redefining them first
 ** Implement the textual export for `TransitionUsage`.
 ** Implement the textual export for `ExhibitStateUsage` such as in:
 +
-```
+[source]
+----
 package root {
     part part1 {
         exhibit state s1 {
@@ -161,7 +167,7 @@ package root {
         }
     }
 }
-```
+----
 ** Implement the textual export for `AllocationUsage` and `AllocationDefinition`.
 ** A limitation has been identified regarding the size of the textual SysML model that can be imported.
 An explicit error message has been added to the upload report to help identify this issue.

integration-tests-playwright/playwright/e2e/diagram.spec.ts

@@ -1,5 +1,5 @@
 /*******************************************************************************
- * Copyright (c) 2025 Obeo.
+ * Copyright (c) 2025, 2026 Obeo.
  * This program and the accompanying materials
  * are made available under the terms of the Eclipse Public License v2.0
  * which accompanies this distribution, and is available at
@@ -45,12 +45,13 @@ test.describe('diagram - interconnection view', () => {
 
     await page.getByTestId('zoom-out').click();
 
-    const compartmentSizeBefore = await interconnectionCompartment.getDOMBoundingBox();
+    const compartmentSizeBefore = await interconnectionCompartment.getReactFlowSize();
 
     await partNode.click();
     await partNode.resize({ height: 20, width: 20 });
 
-    const compartmentSizeAfter = await interconnectionCompartment.getDOMBoundingBox();
-    expect(compartmentSizeAfter.height).toBeLessThan(compartmentSizeBefore.height);
+    const compartmentSizeAfter = await interconnectionCompartment.getReactFlowSize();
+    expect(compartmentSizeAfter.height).toBeGreaterThan(compartmentSizeBefore.height);
+    expect(compartmentSizeAfter.width).toBeGreaterThan(compartmentSizeBefore.width);
   });
 });