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

Diff: swap the order of expected-vs-obtained #875

Merged
merged 1 commit into from
Jan 20, 2025

Conversation

kitbellew
Copy link
Contributor

It was mapping obtained to original, and expected to revised.

It was mapping obtained to original, and expected to revised.
Copy link
Contributor

@tgodzik tgodzik left a comment

Choose a reason for hiding this comment

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

I think it makes more sense, yeah. Though wonder if it could confuse people that expect the old order?

@kitbellew
Copy link
Contributor Author

I think it makes more sense, yeah. Though wonder if it could confuse people that expect the old order?

i would emphasize this in the release notes. this particular approach took me a while to get used to, but the last straw was a recent conversation with @bjaglin where i completely misunderstood his bug report where he shared a simple diff between what was checked in and the actual output.

@kitbellew kitbellew merged commit 15df253 into scalameta:main Jan 20, 2025
9 checks passed
@kitbellew kitbellew deleted the 875 branch January 20, 2025 14:11
@SethTisue
Copy link
Contributor

SethTisue commented Jan 21, 2025

This has subconsciously bugged me for a long time now, but I never thought to suggest it be changed. Thank you!

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