[1033] Remove filter condition on root namespace for diagram creation

Bug: #1033
Signed-off-by: Florian ROUËNÉ <florian.rouene@obeosoft.com>

Author: frouene

CHANGELOG.adoc

@@ -16,6 +16,7 @@
 
 - https://github.com/eclipse-syson/syson/issues/1061[#1061] [general-view] Add ellipsis on `Packages` label, to provide visual feedback on name overflow.
 - https://github.com/eclipse-syson/syson/issues/1007[#1007] Improve direct edit on Feature elements to be able to set the `isDefault` and `isInitial` properties
+- https://github.com/eclipse-syson/syson/issues/1033[#1033] [explorer] Make it possible to create a diagram representation directly under a `root Namespace` element
 
 === New features
 

backend/views/syson-diagram-common-view/src/main/java/org/eclipse/syson/diagram/common/view/services/ViewCreateService.java

@@ -111,7 +111,7 @@ public ViewCreateService(IViewDiagramDescriptionSearchService viewDiagramDescrip
      * @return {@code true} if the diagram can be created on the provided {@code element}
      */
     public boolean canCreateDiagram(Element element) {
-        return !this.utilService.isRootNamespace(element);
+        return true;
     }
 
     /**
@@ -336,14 +336,14 @@ public Element createPartUsageAsActor(Element self, Element selectedObject) {
      * {@link RequirementDefinition}.
      *
      * @param self
-     *            a {@link RequirementUsage} or {@link RequirementDefinition}, otherwise no {@link PartUsage} will be
-     *            created.
+     *         a {@link RequirementUsage} or {@link RequirementDefinition}, otherwise no {@link PartUsage} will be
+     *         created.
      * @param selectedObject
-     *            a {@link ItemUsage} or {@link ItemDefinition} that will be subsetted by (respectively that will type)
-     *            the created {@link PartUsage}.
+     *         a {@link ItemUsage} or {@link ItemDefinition} that will be subsetted by (respectively that will type)
+     *         the created {@link PartUsage}.
      * @return the newly-created {@link PartUsage}, contained by {@code self} through a {@link StakeholderMembership}.
-     *         If {@code self} was neither a {@link RequirementUsage} nor a {@link RequirementDefinition}, {@code self}
-     *         is returned as-is.
+     * If {@code self} was neither a {@link RequirementUsage} nor a {@link RequirementDefinition}, {@code self}
+     * is returned as-is.
      */
     public Element createPartUsageAsStakeholder(Element self, Element selectedObject) {
         Objects.requireNonNull(self);

doc/content/modules/user-manual/assets/images/release-notes-create-diagram-on-root-namespace-element.png

@@ -13,7 +13,10 @@ name is truncated.
 
 image::release-notes-package-name-ellipsis-overflow.png[Package name overflow with ellipsis, width=85%,height=85%]
 
-- In diagrams, the direct edit tool on `Feature` elements now allows to use the ":=" and "default" symbols (see for more details in xref:ROOT:how-tos/model-management.adoc#direct-edit[user documentation] ).
+- In diagrams, the direct edit tool on `Feature` elements now allows to use the ":=" and "default" symbols (see for more details in xref:user-manual:how-tos/model-management.adoc#direct-edit[user documentation] ).
+- It is now possible to create a `General View` diagram under root namespace elements.
+
+image::release-notes-create-diagram-on-root-namespace-element.png[Create diagram on root namespace element, width=50%, height=50%]
 
 == Dependency update
 

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

@@ -153,5 +153,16 @@ describe('Diagram Creation Tests', () => {
         cy.getByTestId('new-representation').should('not.exist');
       });
     });
+
+    context('When we select a root namespace element', () => {
+      it('Then we can create a new representation in it', () => {
+        const explorer = new Explorer();
+        cy.getByTestId('tree-filter-menu-icon').should('exist').click();
+        cy.getByTestId('tree-filter-menu-checkbox-Hide Root Namespaces').click();
+        explorer.getTreeItemByLabel('Namespace').should('exist');
+        explorer.createRepresentation('Namespace', 'General View', 'generalView');
+        diagram.getDiagram('generalView').should('exist');
+      });
+    });
   });
 });