Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expand usage of "config" to "configuration" in most places #525

Closed
wants to merge 12 commits into from

Conversation

jpsim
Copy link
Collaborator

@jpsim jpsim commented Feb 11, 2016

This has a considerable impact on the public API and touches a large part of the codebase. We decided to do this in #507 (which this PR depends on).

There are two places where we still use the "config" abbreviation: the command line --config parameter and the use_nested_configs configuration key. I'd actually suggest that we deprecate the configuration key altogether since when would you ever have nested configuration files without wanting to use them? This should just be the standard behavior IMO.

/cc @scottrhoyt @norio-nomura

@norio-nomura
Copy link
Collaborator

Maybe we should use custom_rules for finding that. 😉

custom_rules:
  config_abbreviation:
    name: "config abbreviation"
    regex: "[cC][oO][nN][fF][iI][gG][^uU]"
    match_kinds:
      - identifier
    message: "config should be disabbreviated!"
    severity: error

@scottrhoyt
Copy link
Contributor

Haha. Love it. 😄

@jpsim
Copy link
Collaborator Author

jpsim commented Feb 12, 2016

rules for all the things! 😛

@jpsim
Copy link
Collaborator Author

jpsim commented Feb 12, 2016

Merging in #527.

@jpsim jpsim closed this Feb 12, 2016
@jpsim jpsim deleted the jp-expand-config branch February 12, 2016 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants