Repository navigation
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
ArdaTkn
force-pushed
the
feat/error-source-locations
branch
from
November 19, 2026 22:45
aca8a32 to
431ab7f
Compare
ArdaTkn
force-pushed
the
feat/error-source-locations
branch
from
November 19, 2026 23:18
431ab7f to
78abd1c
Compare
This branch has not been 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.
Closes #280.
Summary
SKILL.mdwith remediation sections and stable anchors for YAML parse errors and key config validation codes.from_yaml_with_locationsandto_sections_with_locationsinsrc/tablassert/ingests.pyto track exact 1-based(file, line, column)coordinates across YAML mappings/sequences, preservingtemplate:coordinates on inherited keys and raisingYamlParseError(yaml-parse-error) with exact coordinates when PyYAML reports aproblem_mark(never fabricating a line/column when absent).flatten_pydantic_error,GraphValidationError, andSectionValidationErrorinsrc/tablassert/errors.py, and wire them intovalidate_pipeline/validate_graph_pipelineinsrc/tablassert/cli.py.tests/test_error_locations.pyand anUnreleasedchangelog entry inCHANGELOG.md.Local gate
scripts/check_changelog.py --base upstream/main: PASSruff check ./ruff format --check .: cleanpyright: 0 errorsvulture/deptry .: cleanpytest tests/test_error_locations.py tests/test_errors.py tests/test_docs_style.py: 18 passed