Skip to content

Typo fixes in *FileHash tasks#4104

Merged
rainersigwald merged 2 commits intodotnet:vs16.0from
rainersigwald:hashtask-typos
Jan 31, 2019
Merged

Typo fixes in *FileHash tasks#4104
rainersigwald merged 2 commits intodotnet:vs16.0from
rainersigwald:hashtask-typos

Conversation

@rainersigwald
Copy link
Copy Markdown
Member

@rainersigwald rainersigwald added the Area: Tasks Issues impacting the tasks shipped in Microsoft.Build.Tasks.Core.dll. label Jan 28, 2019
Comment thread src/Tasks/FileIO/GetFileHash.cs Outdated
var hash = ComputeHash(Algorithm, file.ItemSpec);
file.SetMetadata("FileHashAlgorithm", Algorithm);

// This typo shipped in 15.8 and 15.9; preserve it for backward compat.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems unlikely anyone was actually using this given there were other issues like #3999. I'm okay if we just fix the name.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I dithered on this and decided to propose the conservative option, but I tend to agree. @livarcocc do you have a preference? It'd technically be a 15.8->16.0 breaking change, but not one that we expect anyone to notice.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's take it.

@rainersigwald rainersigwald changed the base branch from master to vs16.0 January 29, 2019 20:14
@rainersigwald rainersigwald merged commit 7b4337f into dotnet:vs16.0 Jan 31, 2019
@rainersigwald rainersigwald deleted the hashtask-typos branch January 31, 2019 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: Tasks Issues impacting the tasks shipped in Microsoft.Build.Tasks.Core.dll.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants