Repository navigation
[Canvas] Improvements to Expression Editor - #32336
Conversation
|
Pinging @elastic/kibana-canvas |
💔 Build Failed |
|
Design PR here -> cqliu1#3 |
💚 Build Succeeded |
69ec3ef to
6cc6ae9
Compare
There was a problem hiding this comment.
Right! I'll remove it
💔 Build Failed |
💔 Build Failed |
f65e2f2 to
59ff226
Compare
💚 Build Succeeded |
|
Hi there. This is a great feature that keeps it simple while adding a lot of functionality. Great work. When I am looking at this, I noticed the following behavior. Here are some steps to reproduce. Note I am using the eCommerce - Revenue Tracking dashboard.
I don't know if this section is needed in full screen, or perhaps should be a drag out from the right with an arrow to pop it out. What are the thoughts on this section in fullscreen? |
alexfrancoeur
left a comment
There was a problem hiding this comment.
Font size & expand are two much needed features, these look great Catherine! While we're in there, I'd be interested in hearing the groups thoughts on adding a button for previewing a data source from the expression editor. I originally wanted it to help build out custom conditional logic #23162
Probably out of scope for this PR, but thought I'd bring it up if we're making UI/UX improvements.
|
@alexfrancoeur The data preview option would be great and I also agree that it should be tackled in a separate PR. @shaunmcgough We can explore ways to improve that area, but it's going to take a bit of wrangling. Given that, I would vote for moving this change to a separate issue as well. The gap (as it stands) allows for the autocomplete panel to still be functional when it appears above the editor. When we revisit this, I will come up with some options for better utilizing that space - overlay the background content, change the autocomplete to a context menu vs fullwidth panel, etc. |
I actually want to take this farther. I would like you to be able to see what your data looks like at any point in the expression. My thought is we could have a "run until cursor" option somewhere (the auto-complete dialog maybe) so you can just use your cursor to control how much of the expression runs. I'm planning to build a POC of that. |
| })); | ||
| setExpression(exp); | ||
| }, | ||
| setFontSize: ({ setFontSize }) => size => { |
There was a problem hiding this comment.
I've never tried overriding a prop value like that. That's a neat idea.
w33ble
left a comment
There was a problem hiding this comment.
Such a great improvement! Either one of these would have been a welcome addition on their own. LGTM!
|
@shaunmcgough @ryankeairns I opened #32671 re: Shaun's feedback. It makes sense to fullscreen the expression editor to cover up the controls up top. |
* Added font size controls and expand/shrink button to expression editor * style the expression editor controls * Removed debug code
* Added font size controls and expand/shrink button to expression editor * style the expression editor controls * Removed debug code
fwiw, love that suggestion @w33ble |
* Added font size controls and expand/shrink button to expression editor * style the expression editor controls * Removed debug code
Summary
Closes #23934.
Related to #27697.
This PR adds a couple UX enhancements to the expression editor.
adds slider to adjust font size in expression editor

adds maximize/minimize button to expand and shrink the expression

Checklist
Use
strikethroughsto remove checklist items you don't feel are applicable to this PR.- [ ] Documentation was added for features that require explanation or tutorials- [ ] Unit or functional tests were updated or added to match the most common scenarios- [ ] This was checked for keyboard-only and screenreader accessibilityFor maintainers