Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[Feat]: Advanced Source Code Editing for Applications and Modules #2007

Open
@placidic

Description

Is your feature request related to a problem? Please describe.
There are rare situations where Lowcoder applications or modules become corrupted or otherwise uneditable through the current UI, which can be frustrating when manual recovery is needed. Additionally, copying or moving components between applications is cumbersome and often requires API usage, which is not user-friendly. Another pain point is the inability to make bulk edits—currently, users have to update components one by one, which is tedious and error-prone for large changes. I admit that modules are the normal solution in these cases, but as you have more and more nested modules, the overhead causes the application to become much less performant.

Describe the solution you'd like
I would like an advanced feature that allows users to directly edit the source code of an application or module. This "Edit Source" option should be marked as an advanced or experimental feature, with strong warnings about potential risks (such as corruption). This would enable:

  • Manual recovery and repair of corrupted applications/modules.
  • Easy copying/moving of components by manipulating source code directly.
  • Advanced customizations not possible through the UI.
  • Bulk edits: Users could make sweeping changes to multiple components at once, saving significant time and reducing the risk of errors compared to repetitive manual edits.

Ideally, this feature would include:

  • An "Edit Source" button in the application/module settings.
  • A warning dialog before saving any changes.
  • Version history or rollback options.
  • The ability to preview changes before applying them.

Describe alternatives you've considered

  • Using the API to export/import components or manually fix issues (time-consuming and not always possible).
  • Rebuilding applications/modules from scratch (loses data and configuration).
  • Waiting for automated recovery or support interventions (not always practical).
  • Manual bulk edits through the UI (slow and error-prone).

Additional context
This feature is aimed at power users and administrators to enhance flexibility and resiliency, especially in cases of corruption, migration, or large-scale changes.
Example use cases:

  • Fixing a corrupted module that won’t load in the UI.
  • Copying a workflow or component from one application to another by editing the source directly.
  • Applying custom tweaks or optimizations not available in the default interface.
  • Bulk updating: Making changes to many components at once, such as updating configuration values, renaming, or migrating structures.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

        AltStyle によって変換されたページ (->オリジナル) /