Evolution of the PHP branch about json.minify HOT 2 CLOSED

Sounds good to me. Is there any use case which would be broken if your repository php-json-minify, is directly shifted to this repositories php branch?

from json.minify.

@pradyunsg

1. being published on packagist requires composer.json to be adapted, since it references to the fork. Then, I don't know whether a non-default branch (here the php one) can be used on packagist, but here is some info about requiring non-deault branch: https://getcomposer.org/doc/05-repositories.md#vcs
2. being a class rather than a function would be a breaking change. This could be circumvented by creating a class in a separate file, which would just include the original function. The namespace of the class would also need to be changed, since it also references to the fork.
3. Since the namespace of the class should be modified, then, the test should be slightly modified too, in order to point to the newly-namespaced class.
4. API doc should also be generated against the newly-namespaced class.

from json.minify.