LuigiClient.linkManager().navigate() doesn't send query parameters

Description

Using LuigiClient.linkManager().navigate("/some/path?param=test) with path that contains query parameters isn’t working

Is this expected behavior or not? If this is the expected it would be great to have a note in the documentation that is not supported.

I have seen that in the Navigate with Intent it accepts “hash” so I assumed it also accepted query params linkManager().navigate('/#?intent=Sales-settings?project=pr2&user=john')

Expected result

navigate to new page with URL: <host>/some/path?param=test

Actual result

Query param is not send

<host>/some/path

Steps to reproduce

call navigate with query param

Troubleshooting

I am thinking of using addCoreSearchParams

[ndricimrr]

Hi @AlexandarNaydenov , I see your point, I just checked the difference and it seems indeed that the add(get)NodeParams function does not decode properly. I will investigate this further on, and let you know.

[AlexandarNaydenov]

@ndricimrr Hi, the storageManager will not work in my case because I wanted to change the url so it could be saved or sent to someone else and he arrived at the same page. And that can not be done with local storage.

Currently we are using CoreSearchParams, but I have understood that NodeParams is more the “Luigi way” for our case. With addCoreSearchParams and getCoreSearchParams decoding is working perfectly and I would expect addNodeParams and getNodeParams to behave the same. Is it an expected behavior of nodeParams encoding to work differently from coreSearchParams`s one?