If a network slice with invalid name is created, the NMS stays loading

[patriciareinoso]

Describe the bug

The webconsole does not have any restriction about the characters allowed in the network slice name but in the NMS we have this restriction ^[a-zA-Z0-9-_]+$

If we create a network slice using the swagger (which does not follow this restriction) and then, try to open the NMS, the page stays loading .. and does not show the network slice page.

To Reproduce

1. Create a NS using the swagger UI or CURL command using invalid characters like {network-name
2. Go to the Network Slices tab in the NMS.
3. The Network slices page is not shown.

Expected behavior

The network slice pages is shown

Environment

webconsole and NMS from main branches.

Additional context

We may have the same issue with other resources: device groups, subscribers, upfs, gnbs.

I think that the issue here is that webconsole and the NMS are not aligned. The fastest solution would be to remove the restriction to the Getters, and keep those in the Post if we want.
Or we can revisit the webconsole and think if this is a restriction that we would like to impose there (more time)

[ghislainbourgeois]

This issue has been added to the team backlog and will be worked on in the new year.

[Gmerold]

Fixed in omec-project/webconsole#293