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
Currently, users have to input their JSON in plain string format. This comes with a ton of downsides
For people who are not technical they wont really understand what JSON is or how to use it.
Users can mess up the JSON schema and miss a } or , very easily
For JSON_ARR its hard to see all your objects you have in the array
JSON_ARR & JSON_OBJ need better UX that allows people to use UI instead of passing in a plain string.
This will
we can sanitize the JSON to make sure it's correct before sending it to the server.
people can mess up JSON if they use a plain string.
less technical people will be able to interact with it.
they should be able to add and remove objects or properties with buttons.
We do not have to force the user to use the UI for building JSON objects, we can have a "advanced mode" that will allow the user to just put in plain text.
This doesn't have to be in the same PR if we want to push this way to prod, but we need to keep track of that improvement if we decide.
Currently, users have to input their
JSON
in plain string format. This comes with a ton of downsides}
or,
very easilyJSON_ARR
its hard to see all your objects you have in the arrayJSON_ARR
&JSON_OBJ
need better UX that allows people to use UI instead of passing in a plain string.This will
add
andremove
objects or properties with buttons.We do not have to force the user to use the UI for building
JSON
objects, we can have a "advanced mode" that will allow the user to just put in plain text.This doesn't have to be in the same PR if we want to push this way to prod, but we need to keep track of that improvement if we decide.
Originally posted by @HazimAr in #1134 (comment)
The text was updated successfully, but these errors were encountered: