Skip to content

bug: missing keys in ght-config.yml may provide unhelpful feedback #247

@rpocase

Description

@rpocase

i had a ght-config file with the following format. after choosing a job to assign to ght provides a unhelpful error message.

✖ Cannot read properties of undefined (reading 'filter')

ght should do early linting on ght-config.yml to indicate to end users that something may be wrong sooner.

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