-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Action fails when params have EOF characters inside them #8802
Comments
verify if this is already solved with unescape |
Hey team! Please add your planning poker estimate with ZenHub @ajinkyakulkarni @ApekshaBhosale @hetunandu @ohansFavour |
This issue is still present after unescape, verified both in release and production. |
This use case requires smart substitution to be turned on since the input text needs to be escaped for the new lines to be used in the request. We do need an improvement in UX for users to be told when smart substitution is the solve for a problem, but I'll be closing this issue and we can tackle that separately. |
@nidhi-nair smart substitution is only for the request right? Here it seems the response is not escaped |
IIUC, the repro for this was to run the update query with the reference from the update form widgets. The text field contains a |
@nidhi-nair no, the sheet has the \n in the PRODUCTS_ID column and that is returned to the list widget. The button is bound to currentItem.PRODUCTS_ID |
Is there an existing issue for this?
Current Behavior
When a value has
\n
in that caseJSON.parse
seems to fail which in the end causenavigateTo
to fail.Steps To Reproduce
This is a sheet link that has demo data where it is reproducible. https://docs.google.com/spreadsheets/d/1uRnnqyi44h3qtndthbIAMrPsMB6Mm25tVGu-u0sRess/edit?usp=sharing
\n
{{navigateTo(currentItem.SOME_KEY, {},'NEW_WINDOW')}}
Environment
Production
Version
Cloud
The text was updated successfully, but these errors were encountered: