Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request 🛍️: Auto-Pairing Curly Braces in Concerto Model Section #280

Open
surya4419 opened this issue Mar 17, 2025 · 0 comments · May be fixed by #281
Open

Feature Request 🛍️: Auto-Pairing Curly Braces in Concerto Model Section #280

surya4419 opened this issue Mar 17, 2025 · 0 comments · May be fixed by #281

Comments

@surya4419
Copy link
Contributor

Feature Request 🛍️

Implement automatic pairing of curly braces {} in the Concerto model section editor to enhance the editing experience and reduce syntax errors.

Use Case

When users are editing Concerto model sections, the editor should automatically insert a closing curly brace '}' whenever an opening curly brace '{' is typed. This should work for both single-line and multi-line scenarios, maintaining proper indentation and cursor positioning.

Possible Solution

Enhance the Monaco Editor configuration to support auto-pairing specifically for Concerto model sections by implementing language-specific bracket pairing rules. This includes handling nested braces, maintaining proper indentation, and ensuring the feature only triggers in appropriate contexts.

Context

Currently, users need to manually type both opening and closing curly braces, which can lead to syntax errors and unbalanced braces. This feature will improve the development experience by reducing typing errors and ensuring proper brace matching.

Detailed Description

  • Implement auto-insertion of closing brace when opening brace is typed
  • Maintain proper indentation for multi-line brace pairs
  • Support nested brace structures
  • Handle special cases (e.g., inside strings or comments)
  • Ensure proper cursor positioning after auto-pairing
  • Add configuration option to enable/disable this feature
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant