[Watcher UI] Inconsistent query syntax validation between Watcher UI and Console

[elasticmachine]

Original comment by @ppf2:

6.0 Alpha 2

The following is considered valid syntax (and works) if you create the watch using the Console (but it is considered invalid syntax by Watcher UI):

"body": """{"query": {"bool": {"must": {"query_string": {"query": "test"}}}}}"""

Ideally, it will be nice for both editors to support 3 ticks for quotes.

The following is considered valid syntax in both Console and Watcher, but when you actually try to put the watch, it fails.

"body": {"query": {"bool": {"must": {"query_string": {"query": "test"}}}}}

The following works in both:

"body": "{\"query\": {\"query_string\": {\"query\": \"test\"}}}"

[elasticmachine]

Original comment by @ppf2:

@bohyun-e It will be nice to use consistent parsers for Watcher UI and Console. I am having to rewrite watches yet another time for customers because they want to use the Watcher UI, but it's failing syntax left and right.

[elasticmachine]

Original comment by @bohyun-e:

@ppf2 thanks for bringing this up.

cc: @chrisronline @BigFunger as well as @bmcconaghy (welcome! 🎆 )

[elasticmachine]

Original comment by @Rasroh:

cc @elastic/kibana-management

[elasticmachine]

Pinging @elastic/es-ui

[alisonelizabeth]

Duplicate of #21752 and resolved by #57563.