Conversation
Material, process, and measurement runs carry their own template and fall back to the spec's template when it is unset. Ingredient runs carry their own name and labels with the same fallback. The change is additive and bumps the version to 5.1.0. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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
1 participant
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.
Material, process, and measurement runs gain a template field. A run returns its own template when one is set and falls back to the template of its spec otherwise. The platform receives a template only when one is set on the run itself, so payloads for runs without one do not change.
Ingredient runs gain their own name and labels. Each returns the run's own value when set and falls back to the spec's value otherwise. Both round-trip through dump and build.
The change is additive, and specs stay as they are. The platform side that stores and returns these fields is in a separate platform-backend PR.
Tests cover the fallback order and the dump and build round trips. One test checks that register_all writes the template first and the run second. The version moves to 5.1.0 for the new feature.
I ran the full pytest suite at 100% coverage, flake8, the ruff format check, derp, and the docs build with warnings as errors.
🤖 Generated with Claude Code