Conversation
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.
What changed
_Actioncompatibility layer and routed directive handling directly throughCanonicalDirectiveEngine.apply_directive(...)boundary coverage for all directive kinds and representative semantic error casescreate_engine()from the public Python API and updated local callers, docs, fixtures, demos, examples, and tests to useEngine()directly0.9.0dev8Why
_Actionshim unnecessary, so this cleans up the engine internals and keeps tests aligned with the live canonical-directive boundarycreate_engine()did not provide behavior beyondEngine(), so removing it simplifies the public API and keeps the package surface aligned with the implementationChecklist
uv run pre-commit run --all-files)uv run pytest)