Skip to content
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

Radon operator StringMatch is hard to use because field auto formats JSON #1828

Open
tmpolaczyk opened this issue Nov 17, 2022 · 2 comments
Open

Comments

@tmpolaczyk
Copy link
Contributor

The StringMatch operator has two arguments, the first one is a JSON map:

Captura de pantalla de 2022-11-17 10-21-36

It is easy to input a JSON map with one key:

{"data":true}

But when trying to add another key, like

{"data":true,"from":true}

It is not possible to write the comma after the first "true", because sheikah auto formats the JSON and removes the comma. The only way to enter the desired JSON is to use an external editor, and copy-paste the value.

So Sheikah should not remove that comma and let the user write freely.

@aesedepece
Copy link
Member

Actually, for the sake of UX, matches should use a value => bool input component on the UI and form the JSON map from those. Value input should use an HTML input of the appropriate to the data type (which we know), and bools should be introduced through an HTML select box.

@tmpolaczyk
Copy link
Contributor Author

matches should use a value => bool input component on the UI and form the JSON map from those.

True, I always expected something like that, but for this issue I am fine with just being able to input the JSON manually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants