Goodbye manual Composer file editing

[raphaelstolt]

Let Composer modify the composer.json and resolve the library it's latest version.

[coveralls]

Coverage remained the same at 100.0% when pulling f0bf76f8b3288ad6b95ee314712f4526af6c7e88 on raphaelstolt:patch-1 into 0b1d0100a29a26c46a2fe26d2f5d8062922ed239 on brick:master.

[coveralls]

Coverage remained the same at 100.0% when pulling f0bf76f8b3288ad6b95ee314712f4526af6c7e88 on raphaelstolt:patch-1 into 0b1d0100a29a26c46a2fe26d2f5d8062922ed239 on brick:master.

[BenMorel]

I'd like to keep the existing JSON and wording, but feel free to just add right after the JSON:

---

Or just run:

composer require brick/money

---

[raphaelstolt]

I get your point regarding the wording change, but keeping the JSON is obsolete for two reasons:

• adding any dependencies manually is a smell
• the version in the README.md has to be updated with every tagged release you make

So there's not really a case for an or in it.

[coveralls]

Coverage remained the same at 100.0% when pulling 06c573793f233c7595526cae13771e74f1b1c532 on raphaelstolt:patch-1 into 0b1d0100a29a26c46a2fe26d2f5d8062922ed239 on brick:master.

[coveralls]

Coverage remained the same at 100.0% when pulling 06c573793f233c7595526cae13771e74f1b1c532 on raphaelstolt:patch-1 into 0b1d0100a29a26c46a2fe26d2f5d8062922ed239 on brick:master.

[BenMorel]

I don't know about that, I always prefer to keep an eye on my composer.json version constraints manually. Updating the version in the README is not a big deal!

Please keep it as it is for now, but you can add the composer require first:

Just run: composer require brick/money or manually define the following requirement in your composer.json file: ...

[BenMorel]

👍