Add schema snapshotting util and a snapshot test#4594
Merged
Conversation
615cc38 to
096bf63
Compare
current state. The snapshot_ttl function writes the current state of the schema into some output dir, defaulting to `software/tests/snapshot/schemaorg-all-https.ttl`. This file can then be used for a simple snapshot/diff test to avoid accidental changes to the schema. When changing the schema the test fails and the 'golden' file needs to be updated, the updated snapshot is then included into any changes. MARKDOWN=true
MARKDOWN=true
096bf63 to
f89a56e
Compare
MatthiasWiesmann
approved these changes
Nov 20, 2025
pascalfleury
approved these changes
Nov 20, 2025
Contributor
pascalfleury
left a comment
There was a problem hiding this comment.
that's a good start :-)
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.
Adding:
all-httpsturtle version of the current schema.This ensures that changes to the complete schema can be observed easily, including changes/additions to the schema itself as well as any code building the schema.
The test could be a fail fast test to run in CI. We can add an github action to run it separately in a follow up. The test runs with the rest of the tests already, but this is quite slow.
demo: