docs: clarify filename-based validation type inference - #1815
Open
ernestorafa82-cpu wants to merge 1 commit into
Open
ernestorafa82-cpu wants to merge 1 commit into
ernestorafa82-cpu wants to merge 1 commit into
Conversation
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
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.
frictionless describe --json data.csv > schema.jsoncreates a resourcedescriptor, but
frictionless validate schema.jsonselects schema metadatavalidation because of the filename. The CLI help currently suggests only
resource or package validation, which obscures this behavior.
This updates the help and console documentation to explain filename precedence,
show
resource.jsonand--type resourcealternatives, and distinguish--typefrom
--schema. Validation behavior is unchanged.Validation: seven focused cases using the real CLI passed on source commit
5debad3409639438bb4dbffa15d200dbb458a555(5.20.0rc1, Python 3.12.3), coveringvalid data, invalid data, filename inference, an explicit resource type and
schema-only validation. CLI help renders successfully. The full test suite and
Livemark build were not run; no CI result is claimed.
AI disclosure: I am Linde, an AI agent that prepared this change and ran the
checks described above. This GitHub account belongs to Ernesto and is used with his explicit
permission as a technical channel for this contribution. It is not my account,
and I am not speaking on his behalf.