Brick\Money VS fig-standards

For the last couple of years I’ve been using Value Objects in my projects to bring language-level strict types to what would typically be array data structures in my code. From method inputs to JSON API responses, value objects have almost entirely replaced arrays throughout. The ability to get runtime type checking and IDE auto-complete has eliminated many potential bugs, from key typos, to assigning an incorrectly typed value by accident: what type is an “amount” property in a credit card transaction API response? An integer of cents (or other minor units), a Money object such as brick/money or moneyphp/money? Or worst of all, a float?

brick/money: A money and currency library for PHP

1 - Floating point is not always great for money operations and can introduce odd rounding errors - https://www.php.net/manual/en/language.types.float.php - you might want to use something like this: https://github.com/brick/money

He should have said to use Brick/Money https://github.com/brick/money which is based on Brick/Math but is specifically money related.

If you don’t want to do the integer conversions yourself, I highly recommend looking at: https://github.com/brick/money

brick/date-time is great! I personally prefer its interface and functionality over Carbon's. I also really like his money library

Is the most popular, but https://github.com/brick/money is preferrable IMO. One of the reasons is that it handles not just money, but all arbitrary precision calculations independent of currecy via brick/math.

There is also no requirement to follow the PHP-FIG standards. The best thing that is build because of those standards is Composer. The most plugins I downloaded while writing use composer. The problem is that the plugins ship with their own vendor directory. While the standard is to have one vendor directory for the whole project. This results in different packages with the same or different version of it in the plugins. Other CMS's like Craft CMS and Drupal have the same problem where third parties provide plugins, but they are able to use Composer as it should be used.

The namespaces and class names must follow this example.

I would familiarize yourself with the following PHP standards: https://www.php-fig.org

The PHP Standard Recommendation, or PSR for short, from the aforementioned PHP-FIG.

That's what happens if you use a PSR-4 autoloader and not utilise PSR-4 in your project structure 👀 So either use PSR-0 or properly use PSR-4.