You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using addNodeParams from a MFE and then using getNodeParams afterwards from the same MFE, the parameters can be encoded wrongly and the output of getNodeParams is different from the input of addNodeParams.
Expected result
The output of getNodeParams is the same as the input of addNodeParams.
Actual result
Spaces in the input to addNodeParams will be transformed to + in the output of getNodeParams. Might also affect other characters.
Steps to reproduce
Call addNodeParams({q: "test abc"})
Wait for context update
Call getNodeParams()
See the result: {q: "test+abc"}
Changing shouldDesanitise to true in getNodeParams has no effect.
Troubleshooting
dxp metadata-registry 476
The text was updated successfully, but these errors were encountered:
Description
When using
addNodeParams
from a MFE and then usinggetNodeParams
afterwards from the same MFE, the parameters can be encoded wrongly and the output ofgetNodeParams
is different from the input ofaddNodeParams
.Expected result
The output of
getNodeParams
is the same as the input ofaddNodeParams
.Actual result
Spaces in the input to
addNodeParams
will be transformed to+
in the output ofgetNodeParams
. Might also affect other characters.Steps to reproduce
addNodeParams({q: "test abc"})
getNodeParams()
{q: "test+abc"}
Changing
shouldDesanitise
totrue
ingetNodeParams
has no effect.Troubleshooting
dxp metadata-registry 476
The text was updated successfully, but these errors were encountered: