Skip to content

Conversation

@BoldAsLove
Copy link
Contributor

@BoldAsLove BoldAsLove commented Mar 13, 2023

changed "almost any change in behavior could result breaking someone" to be "almost any change in behavior could cause a logic error for a consumer".

Summary

I think the author intended to convey the idea that a change to behavior in a library can cause breaking changes for the consumer of that library, that's why they wrote 'breaking someone'. However, that doesn't read well nor convey the idea well. It reads as though the 'someone' is the thing that is breaking, not their code. I prefer the change to read "almost any change in behavior could cause a logic error", leaving off the 'for a consumer', but will leave that on the change to keep it as close to what I believe was the authors intent.

Fixes #Issue_Number (if available)

Internal previews

📄 File(s) 🔗 Preview link(s)
docs/standard/library-guidance/breaking-changes.md Preview: docs/standard/library-guidance/breaking-changes

changed "almost any change in behavior could result breaking someone" to be "almost any change in behavior could cause a logic error for a consumer".
I very much doubt the author intended to say "breaking someone", maybe "breaking something" and that's why I added 'for a consumer'. Personally I prefer "almost any change in behavior could cause a logic error" but will leave it changed as-is to keep as close to what I believe is the authors intent.
@BoldAsLove
Copy link
Contributor Author

@dotnet-policy-service agree

@ghost ghost added the community-contribution Indicates PR is created by someone from the .NET community. label Mar 13, 2023
@IEvangelist IEvangelist enabled auto-merge (squash) March 13, 2023 22:55
@IEvangelist IEvangelist merged commit 4971b27 into dotnet:main Mar 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

community-contribution Indicates PR is created by someone from the .NET community. dotnet-fundamentals/svc

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants