-
Notifications
You must be signed in to change notification settings - Fork 8
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
Schema tab #155
Schema tab #155
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
However, I see some fields for improvement.
Items listed in the "Schema / Inspect" pane behave like a link, but it is unclear where it points.
For instance, the SchemaCompiledItemDefinition
text leads to the documentation, while definitions switch the inspected item.
WDYT about the following improvements?
- Use the
pointer
cursor while the mouse is over a definition? - Add the
[title]
attribute that explains where it leads, e.g., "Click to see the $block definition."
Also, it would be good to add support for arrow keys. When pressing the down/up arrow, the "Inspect" view switches a definition to preview.
|
||
if ( !definition ) { | ||
return <Pane isEmpty="true"> | ||
<p>Select a schema definition to inspect</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<p>Select a schema definition to inspect</p> | |
<p>Select a schema definition to inspect.</p> |
In the src/schema/pane.js
file, a sentence ends with a dot.
After merging the |
Feature: Introduced the schema tab. Closes #41.
Note: I realize this feature could be better. There could be better ways to visualize dependencies (as a foldable tree), browse attributes and filter the whole thing (gets busy when the editor has GHS). But my intention was to bring something (better than nothing) using UI components we already have and then we can iterate in MVP2. I also know that this should probably be under "Model" tab but because of the design decision we took years ago, there's no space (layout) for this kind of thing. It requires two panels, so it won't fit next to "Markers".