Skip to content

[feature] Add support for the path key for configuration settings #164

@maks-oleksyuk

Description

@maks-oleksyuk

The Readme file contains the following information:

The path to check can be overwritten with the --path option. If the path is one you always need checking you can place it in your peck.json file.

but I couldn't find any examples of how this could be configured and made to work

I expected the configuration to be similar to the following

{
    "preset": "laravel",
    "patch": [
      "app"  
    ]
}

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