Skip to content

Signaling to the user when the tool is called on an incorrect file type #217

@FLKR-redo

Description

@FLKR-redo

I have included the tool in a pipeline without realizing I was calling it on a yaml file without adding the --extensions yaml option (ex. j2lint wrongfile.yaml). Even when running in verbose mode the tool doesn't signal that this error has occurred, so I propose to have it error out when such a mistake happens.

Something like:

$ j2lint wrongfile.yaml

ERROR: 'wrongfile.yaml' is not in extensions list. Add it with '--extensions yaml'

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions