languages: refactor step 1 #593
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
horriblename
reviewed
Feb 1, 2025
This was referenced Feb 1, 2025
This should allow language modules to define new formatters without accessing conform's setupOpts each time.
1 task
|
Closing, as changes from this PR already made it into main branch. |
|
✅ Preview has been deleted successfully! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the first step to the dreaded language refactor. Adds necessary groundwork for refactoring the
languages.*option modules latter on.We would like to rely on conform-nvim and nvim-lint for modular and customizable formatting and linting, and then deprecate none-ls in the second step.
Goals:
Things to do:
Things done: