Repository navigation
feat: export ruleSides and its RuleSides type - #67
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
This security review couldn’t start because the paying account has exhausted its Codex allowance and has insufficient available credits. The payer can check their balance and add credits in the Codex usage dashboard, then try again. If you do not manage the paying account, contact this repository's admins. |
a7ee116 to
a5aac85
Compare
|
@codex security review |
|
This security review couldn’t start because the paying account has exhausted its Codex allowance and has insufficient available credits. The payer can check their balance and add credits in the Codex usage dashboard, then try again. If you do not manage the paying account, contact this repository's admins. |
ruleSides lists the paths a two-way rule reads and writes, the same list the executor and the validator use, so a consumer that has to reason about a crosswalk's paths (to tell whether it can be applied a page at a time, or to show its rules) handles every operation without keeping its own copy of which field of which rule holds a path.
a5aac85 to
34604c7
Compare
|
@codex security review |
|
This security review couldn’t start because the paying account has exhausted its Codex allowance and has insufficient available credits. The payer can check their balance and add credits in the Codex usage dashboard, then try again. If you do not manage the paying account, contact this repository's admins. |
|
🎉 This PR is included in version 0.11.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
ruleSidesalready lists the paths a two-way rule reads and writes for the executor and the validator. Exporting it lets a consumer that reasons about a crosswalk's paths (whether it can be applied a page at a time, how to show its rules) cover every operation without copying which field of which rule holds a path.