-
Notifications
You must be signed in to change notification settings - Fork 275
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
chore!(encryption): rename are_we_the_last_man_standing
to is_last_device
#4522
Conversation
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.
Don't forget the changelog entry. It's a breaking change.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4522 +/- ##
==========================================
- Coverage 85.35% 85.34% -0.02%
==========================================
Files 285 285
Lines 31978 31978
==========================================
- Hits 27295 27291 -4
- Misses 4683 4687 +4 ☔ View full report in Codecov by Sentry. |
…_device` While the former name is arguably more fun, the latter is more descriptive of what the function does.
8a7a922
to
8682d5f
Compare
@@ -28,6 +28,7 @@ All notable changes to this project will be documented in this file. | |||
call `AttachmentConfig::new().thumbnail(thumbnail)` now instead. | |||
- [**breaking**] `Room::send_attachment()` and `RoomSendQueue::send_attachment()` | |||
now take any type that implements `Into<String>` for the filename. | |||
- [**breaking**] `Recovery::are_we_the_last_man_standing()` has been renamed to `is_last_device()`. |
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.
Link to the PR please.
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.
Why? If we require a link to the PR, at this point we should use towncrier, since this would be equivalently painful in terms of DX (i.e. have to push another time after the first push, to figure out what the final PR number is)
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.
Because people find them useful. No, Towncrier has more issues since you, just like with git-cliff, don't incrementally edit the changelog.
While the former name is arguably more fun, the latter is more descriptive of what the function does.