Ricardo M.

I think that it will be better to leave the version downgrade as a last-resort solution since in production mode, there's a console error only.

Just for testing purposes, I downgraded `monaco-editor` to `0.34.1` and I don't see the error message in Firefox :thinking:

My two cents: 1. We should aim to add specific tests in each individual integration and provide a mock Kaoto API to easily ensure that the extensions are interacting with...

The command to run the e2e tests against the sandbox application are: In the kaoto-ui folder, from a separate terminal execute: ```bash yarn workspace @kaoto/sandbox run star --port 1337 --host...

@tplevko you're right, it's the same behavior as `vscode-kaoto`. Definitely It's not ideal neither a desired behavior. It's happening because we have 2 listeners, one from the code editor and...

Yes, it's still happening. This is because the `monaco` editor is a bit complex to run it through the JSDom environment. We're [mocking the whole component here](https://github.com/KaotoIO/kaoto-ui/blob/d30e611a509a08d2268deb63ae7cf90b0ef282d3/src/__mocks__/reactCodeEditorMock.js) In order to...

This is considered to be a low priority at the moment, I'm lowering the priority to reflect this.

Thanks @tplevko for putting this together :+1:

A temporary workaround for e2e was introduced here: https://github.com/KaotoIO/kaoto-ui/pull/1921#discussion_r1222579584

I never thought that I would ever say this, but this is not a bug but a feature :sweat_smile: :see_no_evil: Jokes aside, showing only the first route is the "intended"...