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

[Ingest Pipeline] Processor Editor Item Styling tweak #70786

Merged

Conversation

jloleysens
Copy link
Contributor

@jloleysens jloleysens commented Jul 6, 2020

Summary

Very minor tweaks to the style of the processor editor items. Also includes a fix for a performance regression linked to editing values in the form flyout. This was addressed by adding a container component to pipeline_processors_editor_item.container.tsx and moving the use of context to processor_settings_form.container.tsx.

How to test

  1. Start Kibana
  2. Go to the Ingest Node Pipelines plugin in the management section

Screenshots

Before

Idle state
Screenshot 2020-07-06 at 12 46 21

Editing inline state
Screenshot 2020-07-06 at 12 46 26

Movings state
Screenshot 2020-07-06 at 12 43 09

After

Idle and inline editing state
Screenshot 2020-07-06 at 12 40 33

Moving state (unchanged)
Screenshot 2020-07-06 at 12 42 53

- Moved the move button to the before the processor name
- Cancel button is still after description if there is one
- Made inline text description a bit taller and changed border
  style
@jloleysens jloleysens added v8.0.0 Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more release_note:skip Skip the PR/issue when compiling release notes v7.9.0 Feature:Ingest Node Pipelines Ingest node pipelines management labels Jul 6, 2020
@jloleysens jloleysens requested review from sebelga and mdefazio July 6, 2020 10:50
@jloleysens jloleysens requested a review from a team as a code owner July 6, 2020 10:50
@elasticmachine
Copy link
Contributor

Pinging @elastic/es-ui (Team:Elasticsearch UI)

@sebelga
Copy link
Contributor

sebelga commented Jul 6, 2020

Thanks for adding those change @jloleysens . I can't test it locally right now, but looking at the screenshot it seems that there will be a jump from "idle" to "moving" state as you remove the move icon on the left. Why not just dim the icon while in moving state to avoid this jump?

I personally don't like much the bold text for each of the processor types, this is why I suggested the badge as with the mappings editor. But I agree that this would need a bit more cycles and time to polish so we can leave it for later 👍

@jloleysens
Copy link
Contributor Author

but looking at the screenshot it seems that there will be a jump from "idle" to "moving" state as you remove the move icon on the left. Why not just dim the icon while in moving state to avoid this jump?

Yeah I hear what you are saying, I tend to feel similarly. What are your thoughts on this @mdefazio ?

@mdefazio
Copy link
Contributor

mdefazio commented Jul 6, 2020

I agree that we should keep the move icon present (or in the same place). I was working through something similar to Seb's proposal where the move icon changes to an 'active' state. While having this as 'active' is maybe a bit specific to this prototype sketch, I think it would be nice to have the move icon act as the toggle to stop moving as well.

I think it is important as well that we don't have any jumps in either the processor names or the UI controls.

Screenshot is showing...
Default
Hover
Move processor selected

image

@jloleysens
Copy link
Contributor Author

jloleysens commented Jul 6, 2020

@sebelga @mdefazio Thanks for the feedback both! Here is the moving states with updates to prevent the UI from jumping:

[Edit was sharing an old image]

Screenshot 2020-07-06 at 16 13 40

I went with the X icon as it feels more like a clear shout at the user what this state means. Thanks for recommendation regarding EuiToggleButton. Definitely the component I was looking for.

@jloleysens
Copy link
Contributor Author

@elasticmachine merge upstream

Copy link
Contributor

@mdefazio mdefazio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

General design looks great!

Just some hard px values that I think we can swap out for eui variables that I've commented on.

}
&--cancel {
// Ensure that the cancel button is above the drop zones
z-index: $cancelButtonZIndex;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to use on of our EUI zIndex sass variables here?

- also prevent re-renders basded on contstructing objects on
  each render
We are only interested in the es docs path string in the settings
form component so no need to render for other updates.
Copy link
Contributor

@mdefazio mdefazio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Build metrics

@kbn/optimizer bundle module count

id value diff baseline
ingestPipelines 258 +1 257

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@jloleysens jloleysens merged commit 50a2991 into elastic:master Jul 7, 2020
@jloleysens jloleysens deleted the ingest-pipeline/minor-styling-tweak branch July 7, 2020 17:23
jloleysens added a commit to jloleysens/kibana that referenced this pull request Jul 7, 2020
* Small styling tweaks to processor items

- Moved the move button to the before the processor name
- Cancel button is still after description if there is one
- Made inline text description a bit taller and changed border
  style

* Commit code that moves the cancel move button 🤦🏼‍♂️

* Do not completely hide the move button, prevent ui from jumping

* Update styling and UX of move button; EuiToggleButton

- Bring the styling of the button more in line with this comment
  elastic#70786 (comment)

* use cross icon for cancelling move

* replace hard values with EUI values in SCSS

* Address rerendering triggered by context

- also prevent re-renders basded on contstructing objects on
  each render

* Similarly move use of context to settings form container

We are only interested in the es docs path string in the settings
form component so no need to render for other updates.

Co-authored-by: Elastic Machine <[email protected]>
jloleysens added a commit that referenced this pull request Jul 7, 2020
* Small styling tweaks to processor items

- Moved the move button to the before the processor name
- Cancel button is still after description if there is one
- Made inline text description a bit taller and changed border
  style

* Commit code that moves the cancel move button 🤦🏼‍♂️

* Do not completely hide the move button, prevent ui from jumping

* Update styling and UX of move button; EuiToggleButton

- Bring the styling of the button more in line with this comment
  #70786 (comment)

* use cross icon for cancelling move

* replace hard values with EUI values in SCSS

* Address rerendering triggered by context

- also prevent re-renders basded on contstructing objects on
  each render

* Similarly move use of context to settings form container

We are only interested in the es docs path string in the settings
form component so no need to render for other updates.

Co-authored-by: Elastic Machine <[email protected]>

Co-authored-by: Elastic Machine <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Ingest Node Pipelines Ingest node pipelines management release_note:skip Skip the PR/issue when compiling release notes Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more v7.9.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants