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
represents the same information as the right side split component here:
This second old-style serialized JSON component is currently present on the Automated Rules > Create and Security > Store JMX Credentials > Add views. The new details component is much more pleasing to look at and probably makes it easier for the user to differentiate the different fields they're looking at. With some section renaming or tooltips, the field names required to build a matchExpression can be determined from the new details component pretty easily.
The text was updated successfully, but these errors were encountered:
With some section renaming or tooltips, the field names required to build a matchExpression can be determined from the new details component pretty easily.
Are we putting the field name into the tooltip?
Also, do we still need to keep the codeblock for hints? This is what I have right now:
I think so, maybe something like the JSON path, ex. target.connectUrl as the tooltip on "Connection URL". Or even just replace the "connection URL" section title with target.connectUrl.
Also, do we still need to keep the codeblock for hints? This is what I have right now:
Not necessarily, though I think it's useful to provide a hint of some form somewhere. After #913 it's hopefully self-evident and easy enough that the hint block can be removed.
The right sidebar panel component here:
represents the same information as the right side split component here:
This second old-style serialized JSON component is currently present on the
Automated Rules > Create
andSecurity > Store JMX Credentials > Add
views. The new details component is much more pleasing to look at and probably makes it easier for the user to differentiate the different fields they're looking at. With some section renaming or tooltips, the field names required to build a matchExpression can be determined from the new details component pretty easily.The text was updated successfully, but these errors were encountered: