Repository navigation
refactor(calendar): reuse shared client date calculations - #239
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use
client-core v0.1.0for Young day/week/month bounds and Sunday timetable weeks, preserving Shanghai dates, week conventions and command output. The module graph adds only the shared core.Closes #238. Part of Life-USTC/Life-USTC#109.
Verified on
ec11a989abe60ccd45c1c99ce149975e2e2a3c05: 1,571 passing race-test/subtest events across 23 packages; 19 requirements and 76 native semantic cases; vet, lint, build and OpenAPI generation. Deployment/provenance scripts, Rust format/clippy and 46 tests, and all 16 Go-to-renderd fixture groups also passed.Local worktree builds use
-buildvcs=falsebecause this host's Go VCS lookup selects an invalid parent checkout; CI retains its normal clean-clone build.