Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for a desniff.yml configuration file #113

Open
bogdannbv opened this issue Mar 12, 2024 · 0 comments
Open

Add support for a desniff.yml configuration file #113

bogdannbv opened this issue Mar 12, 2024 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@bogdannbv
Copy link
Member

Similar to what phpunit, phpcs, phpstan etc. are doing, a desniff.yml configuration file should be supported and automatically loaded if present and require CLI arguments only if they're not defined in the config file.

The file should support all the existing CLI arguments.

We should provide a default configuration file that contains the default values for all the existing CLI arguments:

  • <env-file> - .env.example
  • <paths> - ./config
  • --fail-code - 1
  • --warn-with-default - false
  • --ansi - true
  • --quiet - false

The default configuration file should be generated using an init command:

./vendor/bin/desniff init

The configuration file should be automatically loaded if present but also the user should be able to provide it using an argument (-c | --config and --fail-code should become -f:

./vendor/bin/desniff -c desniff.ci.yml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant