upgrade: V13-LOCALE-JIFF-DATES and V13-CAPITAL-INVOICE-JIFF-DATE flag code that already uses jiff
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 32/100
Research direction
Open pull request #847 first: it already targets these two rules, so read it before touching anything. Then find the rule definitions for V13-LOCALE-JIFF-DATES and V13-CAPITAL-INVOICE-JIFF-DATE in the rules directory and see how each matches call arguments, so jiff value types and jiff::/rullst::orm:: paths can be recognised and skipped. Done means --all-rules no longer reports migrated code and the rule's regression test fixtures cover both a flagged and a silent case.
Written by the indexing model from the issue text.
Description
With --all-rules, both rules report as must-change code that already passes jiff values, so an application that finished the migration still sees required changes.
Fix: recognise jiff arguments (types and jiff::/rullst::orm:: paths) and stay silent, with regression tests.
Reported by the maintainer's applications while upgrading to 13.0.0-alpha.6 and adopting its improvements (21 November 2026).
- Dominant language
- Rust
- Stars
- 21
- Forks
- 6
- Avg merge
- 5h 35m
- Merged PRs (30d)
- 246
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Rullst/Rullst
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
Maintainers usually reply within 1 day
-
good first issue help wanted
Difficulty 2/5 Half a day Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
good first issue help wanted
Difficulty 2/5 Half a day Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Validate the Ollama AI provider with a real serverPossibly taken @visy-ani claimed this today. Opengood first issue help wanted
Difficulty 2/5 Half a day Newbie friendliness 70/100
Rullst/Rullst#812 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
eventflux-io/eventflux#203 ·
Maintainers usually reply within 1 day
-
bug ui
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
userFRM/egui-charts#4068 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
trezor/trezor-firmware#8357 ·
Maintainers usually reply within 2 days
-
fuzz-crash review-followup
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day