Patch 2

[konstchri]

Proposed changes

Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.
If it fixes a bug or resolves a feature request, be sure to link to that issue.

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

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc.

[netlify]

👷 Deploy request for lowcoder-cloud pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	be2942b

[FalkWolsky]

Can you please comment what your changes would have as effect and how you intend to change the custom component. From pure code reading - we did not understand fully what your change is about. You can use the standard description area of the PR / Merge Request to describe your change. Than you very much in advance.

As a second wish ... we always only raise PRs to /dev not to /main.
From there we run our tests and only at a release we merge to /main. Please change the destination of the PR to /dev. That would be helpful!