feat: values schema json support and enhanced code editor

[dennisvankekem]

api: linode/apl-api#818

Editor now has error support build in with values.schema.json support!

Screen.Recording.2025-10-15.at.4.00.17.PM.mov

Considerations

• I have tested the changes in both light and dark mode.
• I have considered the need for new unit tests.
• I have tested the changes on a cluster.
• I have included relevant documentation updates.
• I have an approved Figma design or have reflected my changes in Figma
• I have verified that the UI/UX is consistent in major browsers (e.g., Chrome, Firefox, Safari, Edge).
• I have tested the changes for responsiveness in different screen resolutions.
• I have tested expected error states and verified that the user is presented with informative error messages.
• I have tested the feature with unusual or extreme inputs (e.g., very long strings, empty states, clicking a button multiple times quickly).

[ElderMatt]

How hard is it to create a test for the editor based on a simple schema?

[dennisvankekem]

Hard, because the desired outcome is decided visually in the Monaco editor, I could write tests per function, but the functions kind of work in series, it would be a lot of work also because the console doesn't really have a big testing platform as of this writing. If tests are required, I'd highly recommend to make a separate ticket for it, then first finish the remaining UI work for the workloads and then get back to it.

[ferruhcihan]

The validation logic works well and the documentation is great! But the validateAndMark function is quite long. We might consider extracting the error-type handlers into separate (helper) functions to improve readability and reduce technical debt.

[dennisvankekem]

@ferruhcihan your concern for the validateAndMark function being too lengthy is valid, but I would personally keep it in the code editor as is. Currently all the functions for the codeEditor that handle codeEditor logic are present in the codeEditor. I think it's fine for now