Enforce the Wasm consumer lint policy - #15
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Repository: LucaCappelletti94/coderabbit/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #15 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 1 1
Lines 3 3
Branches 3 3
=========================================
Hits 3 3 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|



Lint warnings alone do not enable Clippy's optional stricter groups. The standalone Wasm consumer needs a local policy to enforce those checks without adopting another workspace.
The policy keeps unsafe foreign-function calls available for SQLite interop and requires justified lint expectations. Generated fixture filenames must remain quoted and escaped Rust literals, which requires a narrow formatting exception.