-
Notifications
You must be signed in to change notification settings - Fork 905
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
[API] ability to get consistent hash of ConfigFileSettings class #1612
Comments
gep13
added a commit
to gep13/choco
that referenced
this issue
Jul 14, 2018
- To allow for correctly generating hash code of objects
gep13
added a commit
to gep13/choco
that referenced
this issue
Jul 14, 2018
- To allow for correct generation of hash codes - This will be used to validate changes to chocolatey.config file
I want to say this fixes a bug as well? |
With grabbing the config file and thinking there may be some changes? |
@ferventcoder possibly. A comparison of the hash would still need to be done in order to see if a change had occurred. |
gep13
added a commit
to gep13/choco
that referenced
this issue
Oct 9, 2018
- To allow for correctly generating hash code of objects
gep13
added a commit
to gep13/choco
that referenced
this issue
Oct 9, 2018
- To allow for correct generation of hash codes - This will be used to validate changes to chocolatey.config file
gep13
added a commit
to gep13/choco
that referenced
this issue
Oct 9, 2018
- To allow for correctly generating hash code of objects
gep13
added a commit
to gep13/choco
that referenced
this issue
Oct 9, 2018
- To allow for correct generation of hash codes - This will be used to validate changes to chocolatey.config file
gep13
added a commit
that referenced
this issue
Oct 9, 2018
(GH-1612) Added consistent generation of hash code
ferventcoder
changed the title
Add ability to get consistent hash of ConfigFileSettings class
[API] ability to get consistent hash of ConfigFileSettings class
Mar 13, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need the ability to be able to quickly determine whether something has changed with the chocolatey.config file. This would allow us to make informed decisions about whether something has changed in the configuration since the last time it was inspected. This is typically done through the
GetHashCode
code of an object, however, in order for this to be reliable, some modifications are required to ensure that the results are consistent.The text was updated successfully, but these errors were encountered: