[Nangelov7]

Proposed changes

This PR introduces the initial version of a standalone code editor component that can be integrated into low-code applications. The code editor supports theme switching, syntax highlighting, multi-language support, a minimap for code navigation, sticky scroll for header visibility, code folding for better readability, and a read-only mode for viewing code without editing.

Issue: #1448

Types of changes

What types of changes does your code introduce to Lowcoder?
Put an x in the boxes that apply.

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help!
This is simply a reminder of what we are going to look for before merging your code.
Put an x in the boxes that apply.

• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

[netlify]

👷 Deploy request for lowcoder-test pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	03db9f7

[FalkWolsky]

That is a fantastic idea and a wonderful Initiative!

As Lowcoder internally makes use of an Code-Editor already, could we ask to check if you can realize the component based on it? When we introduce a new Code-Editor, we increase the size of Lowcoder Bundle Files quite a bit - and may have then "2 Code Editors" parallel in Lowcoder.

[iamfaran]

Hi @Nangelov7, thanks for this, we really like the idea!

I've reviewed the code and tested it. Unfortunately, Monaco isn't a good fit for us: Lowcoder relies heavily on CodeMirror, and as Falk mentioned, adding Monaco would significantly increase the bundle size.

While testing I also found an issue: when switching the height property between Auto and Fixed, the code loses its syntax highlighting and shows up as a plain string (tested with JavaScript).