Skip to content

[Ingest Node Pipelines] Implement EuiInlineEdit into Inline Text Input Component#162398

Merged
breehall merged 9 commits intoelastic:mainfrom
breehall:InlineEdit/ingest_node_pipelines
Jul 25, 2023
Merged

[Ingest Node Pipelines] Implement EuiInlineEdit into Inline Text Input Component#162398
breehall merged 9 commits intoelastic:mainfrom
breehall:InlineEdit/ingest_node_pipelines

Conversation

@breehall
Copy link
Copy Markdown
Contributor

@breehall breehall commented Jul 24, 2023

Included in elastic/eui#6778

Summary

Hi team! EUI recently released the EuiInlineEdit component and the Ingest Node Pipelines page was identified as a good candidate for the new component. This PR is replaces the inner workings of the InlineTextInput component and replaces it with the new EuiInlineEdit component.

I've included screens below of this change, but would love to hear your feedback and ensure this component installation meets all of the Ingest Node Pipeline needs.

Ingest Node Pipelines (Read Mode)
4ADF42EF-B796-4ACD-918A-164132117166

Ingest Node Pipelines (Edit Mode)
739AA987-77E3-4D19-B04A-EF97982C41A7


Changes I'd like to call out:

  • There's no tooltip surrounding inline edit that displays the placeholder or text value. EuiInlineEdit includes a title for the read mode button, so the value can be seen on hover. (This feature will make it into the next Kibana upgrade and will not require any additional changes).
  • The placeholder styling is slightly different than the previous version

Design Question:
Should the inline edit to be constrained to the left side of the pipeline? I didn't want to change this aspect without prior input.

Checklist

Delete any items that are not applicable to this PR.

@breehall
Copy link
Copy Markdown
Contributor Author

@elasticmachine merge upstream

@breehall breehall changed the title [Ingest Node Pipelines] (WIP) Implement EuiInlineEdit [Ingest Node Pipelines] Implement EuiInlineEdit into Inline Text Input Component Jul 24, 2023
@breehall breehall added EUI release_note:skip Skip the PR/issue when compiling release notes labels Jul 24, 2023
@breehall breehall marked this pull request as ready for review July 24, 2023 15:20
@breehall breehall requested a review from a team as a code owner July 24, 2023 15:20
@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/eui-team (EUI)

@yuliacech yuliacech self-requested a review July 25, 2023 13:40
Copy link
Copy Markdown
Contributor

@yuliacech yuliacech left a comment

Choose a reason for hiding this comment

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

Thanks a lot for working on this, @breehall!
Tested locally and everything works as expected. I think the design changes are okay with me, because now the field is aligned with the default EUI design.
Regarding your question about input fields being aligned to the left: I'm not aware of a specific reason for that. Looking at a long text, it might be better to allow the field to expand to full width. I think it would be okay to do in a follow up PR if you'd like to.
Only a minor comment regarding code changes: I don't think that we need the wrapping InlineTextInput component anymore and could directly use EuiInlineEdit in the PipelineProcessorsEditorItem component.

@breehall
Copy link
Copy Markdown
Contributor Author

@elasticmachine merge upstream

@kibana-ci
Copy link
Copy Markdown

💚 Build Succeeded

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
ingestPipelines 298 297 -1

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
ingestPipelines 362.3KB 361.1KB -1.2KB

History

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

@breehall breehall merged commit 618c7fa into elastic:main Jul 25, 2023
@kibanamachine kibanamachine added v8.10.0 backport:skip This PR does not require backporting labels Jul 25, 2023
ThomThomson pushed a commit to ThomThomson/kibana that referenced this pull request Aug 1, 2023
…put Component (elastic#162398)

Included in elastic/eui#6778

## Summary
Hi team! EUI recently released the `EuiInlineEdit` component and the
Ingest Node Pipelines page was identified as a good candidate for the
new component. This PR is replaces the inner workings of the
`InlineTextInput` component and replaces it with the new `EuiInlineEdit`
component.

I've included screens below of this change, but would love to hear your
feedback and ensure this component installation meets all of the Ingest
Node Pipeline needs.

**Ingest Node Pipelines (Read Mode)**

![4ADF42EF-B796-4ACD-918A-164132117166](https://github.com/elastic/kibana/assets/40739624/3d43e45f-9149-4ce8-9f4c-3c7c4bafcc88)


**Ingest Node Pipelines (Edit Mode)**

![739AA987-77E3-4D19-B04A-EF97982C41A7](https://github.com/elastic/kibana/assets/40739624/9abddf40-8e76-4c34-b5e8-31578e655f3f)

---

Changes I'd like to call out:
- There's no tooltip surrounding inline edit that displays the
placeholder or text value. `EuiInlineEdit` includes a `title` for the
read mode button, so the value can be seen on hover. (This feature will
make it into the next Kibana upgrade and will not require any additional
changes).
- The `placeholder` styling is slightly different than the previous
version

Design Question:
Should the inline edit to be constrained to the left side of the
pipeline? I didn't want to change this aspect without prior input.



### Checklist

Delete any items that are not applicable to this PR.

- ~[ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)~
- ~[ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials~
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [x] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [x] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))
- ~[ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~
- [x] This renders correctly on smaller devices using a responsive
layout. (You can test this [in your
browser](https://www.browserstack.com/guide/responsive-testing-on-local-server))
- [x] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers)

---------

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip This PR does not require backporting EUI release_note:skip Skip the PR/issue when compiling release notes v8.10.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants