addons/namingng: rename config file to namingng.json #5796
Closed
+5
−5
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
Confusingly, the config file for namingng.py was named naming.json, while another addon naming.py can be used using a *different* file that is also named naming.json, residing in a different directory. By renaming the config file to namingng.json, it is made explicit that this file belongs to the namingng.py addon.
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.
Confusingly, the config file for namingng.py was named naming.json, while another addon naming.py can be used using a different file that is also named naming.json, residing in a different directory.
By renaming the config file to namingng.json, it is made explicit that this file belongs to the namingng.py addon.