create composer package

[schmunk42]

This code does magic!

Could you create a composer package and make it available via vendor/bin

• https://getcomposer.org/doc/
• https://getcomposer.org/doc/articles/vendor-binaries.md

[cmrcx]

Thanks for the suggestion. Is this what you expect? I'm not sure what sense the vendor binary makes in this project.

[schmunk42]

The change looks good, just one thing to note... Most files in vendor/bin don't use the .php extension.

What's about adding a wrapper to accomplish this, so we could run vendor/bin/phptidy in the end, while maintaining BC.

[cmrcx]

I'm still not sure what the sense of this vendor binary thing is. Can you please describe a use case with phptidy, in which the composer package and the vendor binary link are helpful?

[schmunk42]

So I have the code generator mentioned above.
It's generating PHP code, but it's hard to maintain a beautiful source code.

In the generator extension I would like to require cmrcx/phptidy with composer.
When giiant gets installed, phptidy gets installed and its "binary" is placed into vendor/bin and I can execute it in my extension, after code-generation, from this specific location and I don't have to worry if you may change the path in the future.

It's basically a standardized system of composer providing CLI scripts, in my current project the vendor/bin looks like this:

• apidoc (Yii 2.0 doc generator CLI)
• markdown
• markdown-latex
• php-cs-fixer (code-style fixer, similar to yours, but without indentation)

[schmunk42]

Moreover ... you can install it globally with composer global require ..., so it's usually available in your PATH then.

[schmunk42]

👍 😄

[schmunk42]

Will you create a package on packagist?

[cmrcx]

Done. Thanks for reminding me.

[schmunk42]

Great! Would also be nice, if you could create a 2.15 tag, since composer/packagist only reads tags, when a composer.json file is present.

[cmrcx]

Done