refactor(formatter): remove keyword_case option
#108
Merged
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
Signed-off-by: azjezz <azjezz@protonmail.com>
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.
📌 What Does This PR Do?
This PR removes the
keyword_caseoption from the formatter configuration.🔍 Context & Motivation
The
keyword_caseoption allowed users to control the casing of keywords (e.g.,class,function,if) in the formatted output. However, this option is rarely used, and changing the casing of keywords can lead to code that deviates from standard conventions.This PR removes this option to simplify the formatter configuration and ensure that keywords are always formatted in lowercase, promoting consistency and adherence to common practices.
🛠️ Summary of Changes
📂 Affected Areas
🔗 Related Issues or PRs
📝 Notes for Reviewers