# Kibana logstash pipelines editing multi line **URL:** \ **Category:** Kibana\ **Created:** [October 16, 2023, 12:32pm UTC](https://discuss.elastic.co/t/kibana-logstash-pipelines-editing-multi-line/345103 "2023-10-16T12:32:35Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![PeterDK](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/peterdk/32/49432_2.png) [@PeterDK](https://discuss.elastic.co/u/PeterDK)\ **Post date:** [October 16, 2023, 12:32pm UTC](https://discuss.elastic.co/t/kibana-logstash-pipelines-editing-multi-line/345103/1 "2023-10-16T12:32:35Z")
Hi, anyone noticed the UI change when editing logstash pipelines? Not only the font (size) has changed (way too large in my opinion), but also the behavior. You can duplicate lines with shift+alt+arrow key, moving line with alt and normally you were able to edit multiple lines with crtl+alt+arrow key. But that doesn't seems to be possible anymore. And that's just very useful to put multiple lines in or out of comment for example We are running Kibana 8.10.2 at the moment. ---
**Author:** ![jsanz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsanz/32/53734_2.png) [@jsanz](https://discuss.elastic.co/u/jsanz)\ **Post date:** [October 24, 2023, 4:42pm UTC](https://discuss.elastic.co/t/kibana-logstash-pipelines-editing-multi-line/345103/2 "2023-10-24T16:42:53Z")
Hi, I'm pretty sure what you've noticed is the migration from the old editor based in [Ace](https://ace.c9.io/) to the new one based in [Monaco](https://microsoft.github.io/monaco-editor/). > > > Fixes https://github.com/elastic/kibana/issues/155842 > > \## Summary > > This PR r…emoves the dependency it has on ace editor in favour of Monaco. Note that \`CodeEditor\` is a kibana wide abstraction built on top of Monaco and located at \`@kbn/kibana-react-plugin/public\`. > > \*\*How to test\*\* > 1. Start elasticsearch with \`yarn es snapshot --license=trial -E path.repo=/tmp/es-backups\` and kibana with \`yarn start\` > 2. Navigate to \`Stack Management\` -\> \`Logstash\` -\> \`Create Pipeline\` > 3. Verify that the editor is Monaco > > \ > \Screenshots\ > > // Before > !\[Screenshot 2023-07-28 at 11 15 44\](https://github.com/elastic/kibana/assets/1191206/a3cc31b7-ffb1-4caa-8dbb-5024a2348a13) > > // After > !\[Screenshot 2023-07-28 at 11 15 39\](https://github.com/elastic/kibana/assets/1191206/9e4bb832-81c1-4012-a991-ea8664d1a47a) > > > \ More context about this long process of migrating from one to the other here > > > I am opening this issue in the Kibana repository (not EUI), since it also contai…ns one component that lives (currently) purely in the Kibana repository. I have the feeling we currently don't have a good guideline when to use \`EuiCodeBlock\`, \`EuiCodeEditor\` (under the hood ACE) and \`CodeEditor\` (from the \`react\_utils\` plugin, under the hood Monaco). > > We've been using \`EuiCodeBlock\` very often when purely showing some Code (e.g. JSON from requests/responses). We've seen significant performance issues with this component, that it freezes the browser completely when trying to render some larger JSON (see also https://github.com/elastic/eui/issues/1208). We ran into the same issue in the currently WIP \[Vega inspector\](https://github.com/elastic/kibana/pull/70941) when trying to render the Vega spec. Despite performance (which can be addressed), the \`EuiCodeBlock\` also is very static and offers not much features, e.g. no collapsing of JSON (https://github.com/elastic/kibana/issues/59949) or no line numbers (https://github.com/elastic/kibana/issues/69614), which are missed by users. > > \`EuiCodeEditor\` is using ACE under the hood, and I think we might be a bit better of nowadays with Monaco (given the larger community with VSCode around it, and thus hopefully better accessibility and extensibility in the long run). > > We now switched the Vega inspector to use \`CodeEditor\`, but I still think it would be beneficial if we could setup some general guidelines around the usage of those 3 components. > > I would suggest the following and would be interested for feedback (especially from the design team): > > \* If you just want to represent a more or less static code snippet (max length around 15 lines) use \`EuiCodeBlock\`. > \* If you need capabilities to edit, or want to print longer code (or potentially don't know how long, because you're printing JSON from APIs), use \`CodeEditor\`. > \* Don't use \`EuiCodeEditor\` for new places more, and instead favor \`CodeEditor\`. > > cc @alexwizp @elastic/kibana-design @kertal ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 21, 2023, 4:43pm UTC](https://discuss.elastic.co/t/kibana-logstash-pipelines-editing-multi-line/345103/3 "2023-11-21T16:43:48Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.