Ricardo M.

AtlasMap used Netlify for previewing purposes.

For context, the `annotations` field for `Kamelets` is located at the `metadata` property, whereas the `description` one is located at the `spec.definition` one. Since the `MetadataEditor` is only handling the...

Part of the issue might be obsolete, but since we still would like to add traits and stuff, we might benefit of having the metadata editor

Pending to decide which alternative we want to follow

For context, this is documented in the Camel LSP, but we don't have it in the Camel Extension pack here: https://github.com/camel-tooling/vscode-camel-extension-pack

@igarashitm , I'm moving this issue to the backlog, since I think after your last comment, it's no longer blocked 👍 (also I agree with it 😃)

This would be a nice addition @tplevko :+1: , this needs to be handled in the https://github.com/KaotoIO/uniforms-patternfly repository in the same fashion as we're doing it for TextField

Potential implementation #1: When double-clicking, the editing field should be bound to the description field. Once is set, show that as the node's label (already implemented)

Related docs: https://ajv.js.org/guide/formats.html#user-defined-formats

This could be done at the plugin side, like we're doing for entities and EIPs