Working with stdin

[DavidBiesack]

Does (should) validate work with stdin for either the schema or instance paths on the command line, or does it require an actual file with a file name and extension?

(It is common for CLI tools, at least in Unix/Linux systems, to accept the file name - to mean "stdin")

I tried

$ my-long-pipline-yielding-a-JSON-schema | jsonschema validate - invalid.yaml
error: No such file or directory
  at file path /private/tmp/-

This works on shells (like bash) that support <(pipeline) to yield named pipes but it is more cumbersome to use:

jsonschema validate <(my-long-pipline-yielding-a-JSON-schema) valid.yaml

(in my case, bash on Mac OS, bash yields a filename such as /dev/fd/63 )

However, even that notation does not work with a pipeline that yields YAML instead of JSON

jsonschema validate <(my-long-pipline-yielding-a-JSON-schema-as-YAML) valid.yaml
unexpected error: Expected YAML document start
Please report it at https://github.com/sourcemeta/jsonschema

That is, `jsonschema' appears to assume JSON if the "file name" ( a named pipe in this case) does not end with .yaml)

[jviotti]

Hey @DavidBiesack , we actually have this open: #614 addressing exactly this. Hopefully we manage to merge it soon!

[DavidBiesack]

Thanks @jviotti -- that appears to work for the instance, but not the schema:

validate accepts instances from stdin only; schemas must be file paths.

my suggestion would be allowing - for the CLI option for either (only one file may be passed via - / stdin )
(just a suggestion to meet expected CLI conventions)

[jviotti]

Yes, we will allow - anywhere!