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
I have checked "open" AND "closed" issues and this is not a duplicate
Description
When changing the field type after having clicked on preview or export does not cause a cache invalidation. This results in Json being given to the user which does not conform to their specification when clicking on preview/export again.
Steps to Reproduce
Include any relevant details like:
Go to JsonGenerator
Set the field names and their types
Open preview or click export.
Change one of the types without adding or removing a field, or changing the field name.
Click on preview or export again and observe the incorrect Json being provided
Screenshots
No response
Do you want to work on this issue?
Yes
If "yes" to above, please explain how you would technically implement this
Update the cache checking function in utils.js to take into account a change in field type, not just field name
The text was updated successfully, but these errors were encountered:
Hello! 👋 Thanks for opening this issue. We appreciate your feedback and will look into it as soon as possible. Feel free to add more details if necessary.
Has this bug been raised before?
Description
When changing the field type after having clicked on preview or export does not cause a cache invalidation. This results in Json being given to the user which does not conform to their specification when clicking on preview/export again.
Steps to Reproduce
Include any relevant details like:
Screenshots
No response
Do you want to work on this issue?
Yes
If "yes" to above, please explain how you would technically implement this
Update the cache checking function in utils.js to take into account a change in field type, not just field name
The text was updated successfully, but these errors were encountered: