Enforcing projects have a composer.json

[Tim Millwood]

Is there any scope for PSR to help enforcing all PHP projects have a composer.json file?

[Alexander Makarov]

I doubt it... it can't be technically enforced.

[Larry Garfield]

Not really. A composer.json file is a Composer thing, and FIG doesn't
run/manage/control Composer. Standards for "what dozen integration
files you should have in your project root" are too volatile for a PSR,
and tie into too many networks outside of our control.

> --
> You received this message because you are subscribed to the Google
> Groups "PHP Framework Interoperability Group" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to php-fig+u...@googlegroups.com
> <mailto:php-fig+u...@googlegroups.com>.
> To post to this group, send email to php...@googlegroups.com
> <mailto:php...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/php-fig/bca5cd55-1a12-4e73-a0ef-603ddc217130%40googlegroups.com
> <https://groups.google.com/d/msgid/php-fig/bca5cd55-1a12-4e73-a0ef-603ddc217130%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

--
--Larry Garfield

[Korvin Szanto]

It could be worthwhile to define a standard file name and format for interop related values parallel to composer.json. Would it be helpful to have a standard option storage location like "fig.json"? For example, PSR-10 could define a format for storing the URI for your security disclosure atom feed.

To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/5592E279.70908%40garfieldtech.com.

[Bernhard Schussek]

I think it would make more sense to add that to composer.json. There's no need to add another configuration file here. Also I don't think that a PSR needs to "enforce" projects to disclose their Atom feed in composer.json/fig.json/whatever. 

--

Bernhard Schussek
Blog: http://webmozarts.com
Twitter: http://twitter.com/webmozart

To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CANeXGWV08mf4cGE%2B9tdoY7YUGaqEP4fqXPKs950zSf8UaZbEzA%40mail.gmail.com.

[Korvin Szanto]

Definitely didn't mean to suggest we enforce anything like that, just recommend a standard name and format with the idea that composer.json would instead try to migrate to this standard file.

To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAHjTTqNfRk5qpJFU0DXd%2B0yRtvK-hL5aEzYTQtezqQDH2Z1R7w%40mail.gmail.com.