observablehq / observablehq/notebook-kit
Allow disabling "autoCloseBrackets" (or, possibility of light customization of CodeMirror settings)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 371
- Forks
- 27
- Avg merge
- 3h 52m
- Merged PRs (30d)
- 1
Description
Observable Desktop is wonderful! Now that I'm using it more I have another request in the same spirit as https://github.com/observablehq/notebook-kit/issues/37 and https://github.com/observablehq/notebook-kit/issues/62 - it would be awesome if there was a way to do some basic customization of the editing experience.
Over the past few days I've noticed myself tripping over this behavior, though I know some people like it:
https://codemirror.net/docs/ref/#autocomplete.closeBrackets
(I'm not 100% sure this is the linked behavior, but it seems related)
I don't usually program with bracket matching of any sort, and right now I'm switching between Sublime Text and Observable Desktop where the behaviors are different, so while it's a reasonable editor behavior it would be amazing if there was some way to customize this and other basic settings, to help those of us who switch between editors multiple times a day.
- Zed has a setting for this
- Sublime text has a setting
- VSCode does too
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names CodeMirror's autocomplete.closeBrackets setting but no repository file, entry point, or test. First locate where the editor is configured, then assess how a user-facing option could disable auto-closing without expanding into unspecified customization; done means the requested behavior can be controlled and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- desktop-dev, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100