Repository navigation
chore: upgrade @minigraf/browser to 2.0.1 and revert #298 workaround - #43
Merged
Merged
Conversation
2.0.1 keeps the same JS API and file format (v7). It fixes literal keyword bindings in rule calls (minigraf#298), string ordering in predicates, and keywords that end in `?`. Revert o3-s2 and o3-s3 to call reports-to with a literal keyword, as the lessons did before 4d9730f. Keep the other workarounds. minigraf#287 is still open (fix planned for v3.0.0), so l1-s3 keeps its split transacts. minigraf#297 still reproduces in 2.0.1 when a recursive rule calls another user-defined rule ("Unbound variable in rule head: ?mid"), so sl3-s3 and t3-s3 keep the pattern-bind form. Refs #40 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DfYD1KuzjcyDCnV7JAi68v
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Summary
@minigraf/browserfrom 1.2.0 to 2.0.1. The JS API and the file format (v7) are the same, so data saved in users' browsers still opens.reports-towith a literal keyword again (:alice,:bob), as before 4d9730f. 2.0.1 fixes bug: literal keyword bound in rule call resolves as entity UUID, silently mismatches keyword values in rule body minigraf#298.What 2.0.1 fixes for users
[(< "a" "b")]and other string comparisons now work. In 1.2.0 they matched nothing.?(for example:person/alive?) now parse.One behavior change: 2.0 rejects extra arguments after the query vector.
(query [...] :max-results 5)is now an error. The lessons and the tutor prompt already put:max-resultsinside the vector, so nothing in the app breaks.Workarounds kept
Unbound variable in rule head: ?mid. I reopened minigraf#297 with a small repro.This change does not close #40. It only covers the #298 part.
Testing
npm test: 224 tests pass. This includes the 66 e2e lesson steps against the real 2.0.1 WASM.npm run build: passes.libcfields.Refs #40
🤖 Generated with Claude Code
https://claude.ai/code/session_01DfYD1KuzjcyDCnV7JAi68v
Generated by Claude Code