Support configuration via configuration file

[raphaelstolt]

Since the number of options keeps growing it would be considerable to allow their configuration via a dedicated configuration file. Whether this happens via a programmtic approach, like done by the PHP Coding Standards Fixer or via a configuration format of choice e.g. yaml, json or ini is up to you.

[vpassapera]

Maybe I can take a look at this and implement something.

I guess I'll start by implementing a yaml configuration, and then move on from there?

Would that be acceptable? (e.g. a PR for each type of configuration format)

[povils]

Hey, thanks for interest :)
I'm not sure what do you mean by each type of configuration format?:)
YAML is more than enough

[cavo789]

Hello

First, thank you so much for your tool ! Really useful.

Like Raphael, I would appreciate the possibility to have a configuration file (like f.i. phpmnd.json) where I can define, for instance (my need), which folders / files should be ignored.

Why ? Because I'm using a global phpmnd.cmd (under Windows) script where I've put my logic for all my repositories and, in any of my repo, I've create a symlink to my global phpmnd.cmd file. So, I can't change the file to work on a specific repo.

By supporting a configuration file, I'll be able to do something like --config %currentdir%/phpmnd.json like I did for others PHP quality tools (phpcs, phpstan, phan, and many others).

Do you think such feature can be added?

Many thanks in advance!

[MGatner]

Also keen on this feature! It really helps when templating across multiple repos.