-
Notifications
You must be signed in to change notification settings - Fork 654
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
Feature/3101 rename config to configuration #3226
Feature/3101 rename config to configuration #3226
Conversation
…ersion.Model.Configuration to GitVersion.Model.Configurations.
…r name config to configuration.
Agree with that |
Okay no problem. I can change it back. I did the namespace change because otherwise the namespace conflicts with the class name. Actually I think we are in the domain of GitVersion to name the class GitVersionConfiguration or GitVersionContext seem for me technically motivated. What about OverallConfiguration!? ;) |
As the configuration file is named
Not a fan, sorry. |
@HHobeck I think we need to rename more classes that contain the prefix or suffix Config for example in the folder https://github.com/GitTools/GitVersion/tree/746efd9290c5ca5fc0164ceecc3b4668adda9c68/src/GitVersion.Core/Configuration, or some of the Unit test class names, do you agree? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! 👏🏼
src/GitVersion.Core/Configuration/Abstractions/IConfigProvider.cs
Outdated
Show resolved
Hide resolved
src/GitVersion.Core/Model/Configuration/GitVersionConfiguration.cs
Outdated
Show resolved
Hide resolved
…iguration, GitVersionConfiguration and IgnoreConfiguration from Model.Configuration to Configuration namespace.
There are a couple of other classes to be renamed: |
…ull values in implementing ConfigurationProvider.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good! 👍🏼
src/GitVersion.Core.Tests/Configuration/IgnoreConfigurationTests.cs
Outdated
Show resolved
Hide resolved
Okay I'm done please take a look and give me feedback. I would prefer to hold on and not to refactor anything else in the PR. |
Please also notice the implementation of ScratchConfigurationBuilder (I'm not sure if EmptyConfigurationBuilder is maybe better!?) and GitFlowConfigurationBuilder. In my opinion this should be used for unit and integration tests. |
…gurationBuilder. Rename SratchConfigurationBuilder to EmptyConfgiruationBuilder.
This reverts commit 56bca3c.
@asbjornu when you're done with the review please merge this one |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Marvellous work @HHobeck! 👏🏼
Thank you @HHobeck for your contribution! |
🎉 This issue has been resolved in version 6.0.0 🎉 Your GitReleaseManager bot 📦🚀 |
Description
This is a refactoring step without any business logic change.
Related Issue
no related issue.
Motivation and Context
Refactoring of Configuration to have clear naming.
How Has This Been Tested?
All unit and integration tests have been executed.
Screenshots (if appropriate):
Checklist: