feat(editorconfig): add support for additional languages and DRY refactor #14
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
…ctor - Refactored .editorconfig to follow DRY principles by consolidating common settings. - Added support for additional languages including Rust and Clojure. - Set default indent size to 4 spaces, with overrides for specific file types to 2 spaces. - Configured shell scripts to use tab indentation. - Included settings for Markdown, Python, Java, PHP, Node.js, and Go files. - Ensured consistent coding styles across various file types and projects. Signed-off-by: Thomas Vincent <[email protected]>
thomasvincent
changed the title
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.
Problem/Goal: The existing .editorconfig file had some redundancies and lacked support for additional programming languages and file types. The goal is to refactor the file to follow the DRY (Don't Repeat Yourself) principle, add support for more languages, and ensure consistent coding styles across various file types and projects.
Relevant Systems: This change impacts all projects and development environments that use the .editorconfig file for maintaining consistent coding styles.
Impact: By refactoring the .editorconfig file, we can improve maintainability, reduce redundancy, and ensure consistent coding styles across different programming languages and file types. This will enhance the overall quality and readability of the codebase.
Acceptance Criteria:
Related Issues/PRs: N/A
Branch Name Suggestion: feature/editorconfig-refactor
Additional Notes:
Refer to the EditorConfig documentation (https://editorconfig.org/) for best practices and guidelines.
Test the refactored .editorconfig file with various file types and editors to ensure compatibility and correct behavior.
Consider adding more language-specific configurations as needed in the future.