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

0.5.x: Remove everything deprecated #1394

Merged
merged 16 commits into from
Feb 2, 2024

Conversation

pitdicker
Copy link
Collaborator

@pitdicker pitdicker commented Jan 28, 2024

Remove everything that is deprecated on the 0.5 branch.

I was wondering if it was better to rename the replacement methods at the same time as removing the deprecated methods, or to leave that for another PR. I.e. renaming things like FixedOffset::east_opt to FixedOffset::east.

Copy link

codecov bot commented Jan 28, 2024

Codecov Report

Attention: 7 lines in your changes are missing coverage. Please review.

Comparison is base (6e8c150) 93.51% compared to head (69a665f) 94.16%.
Report is 1 commits behind head on 0.5.x.

Files Patch % Lines
src/datetime/mod.rs 90.90% 2 Missing ⚠️
src/datetime/serde.rs 95.45% 1 Missing ⚠️
src/format/parsed.rs 92.85% 1 Missing ⚠️
src/naive/datetime/serde.rs 95.45% 1 Missing ⚠️
src/naive/time/mod.rs 98.96% 1 Missing ⚠️
src/offset/fixed.rs 90.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##            0.5.x    #1394      +/-   ##
==========================================
+ Coverage   93.51%   94.16%   +0.65%     
==========================================
  Files          34       34              
  Lines       17018    16824     -194     
==========================================
- Hits        15914    15842      -72     
+ Misses       1104      982     -122     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@pitdicker pitdicker force-pushed the remove_deprecated branch 3 times, most recently from de6a518 to e9bba9c Compare January 28, 2024 20:39
@pitdicker
Copy link
Collaborator Author

pitdicker commented Jan 28, 2024

We may want to backport the first two commits (documentation and test fixes) to the 0.4 branch.

@djc
Copy link
Contributor

djc commented Jan 29, 2024

We may want to backport the first two commits (documentation and test fixes) to the 0.4 branch.

That sounds good to me.

@djc
Copy link
Contributor

djc commented Jan 29, 2024

I was wondering if it was better to rename the replacement methods at the same time as removing the deprecated methods, or to leave that for another PR. I.e. renaming things like FixedOffset::east_opt to FixedOffset::east.

Yes, I think we should do that in the same commit.

@pitdicker pitdicker force-pushed the remove_deprecated branch 7 times, most recently from 8acce1a to ad308cc Compare January 29, 2024 11:37
@pitdicker
Copy link
Collaborator Author

Because the renames are touching so many lines I split them out in separate commits. Easy to squash if you do prefer them combined though.

I don't really want to make a lot of changes to the file for NaiveDate because I think it would create a messy merge conflict the open PR to refactor that file. So I skipped the renames there for now.

@pitdicker pitdicker added the API-incompatible Tracking changes that need incompatible API revisions label Jan 31, 2024
@pitdicker pitdicker mentioned this pull request Feb 2, 2024
@pitdicker pitdicker merged commit 03afcba into chronotope:0.5.x Feb 2, 2024
37 checks passed
@pitdicker pitdicker deleted the remove_deprecated branch February 2, 2024 11:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API-incompatible Tracking changes that need incompatible API revisions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants