feat(console): Create backend endpoint for updating a section

[aqibmohammadkhan]

Issue

https://gravitee.atlassian.net/browse/APIM-11947

Description

• created endpoint and its use case that updates attributes of a navigation item
• It can update title for a PAGE, LINK and FOLDER
• it can update url or title or both for LINK

{{baseURL}}/portal-navigation-items/{{navigationId}}

sample payload for update page with required fields

{
    "title": "Update title",
    "type": "PAGE",
    "order": 4
}

Screen.Recording.2025-11-21.at.11.57.12.mov

Response

{
    "type": "LINK",
    "url": "yahoo.com",
    "id": "70dcfdcd-0b83-43fb-aa9f-7d948295742c",
    "organizationId": "DEFAULT",
    "environmentId": "DEFAULT",
    "title": "this is updated title",
    "area": "TOP_NAVBAR",
    "order": 4
}

Additional context

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[jourdiw]

Personally I try to avoid mocking the use cases for the resource tests. One of the great advantages with the Onion architecture is that we can have better confidence for the end to end functionality.

WDYT about not mocking the use cases for the resources?

[aqibmohammadkhan]

Personally I try to avoid mocking the use cases for the resource tests. One of the great advantages with the Onion architecture is that we can have better confidence for the end to end functionality.

WDYT about not mocking the use cases for the resources?

I agree. This was already done, so i just added my changes below that. I have removed all the new created use cases now and mocking the in-memory crud and other services.

[jourdiw]

Nice job!

A couple things if you are feeling 🚀 :

• Use core-based exceptions in the services rather than the InvalidDataException
• Removing page content id from the Update model in the core package to match what is expected from the Resource 👍