spatie.be VS credo

How do you debug your code in PHP? Do you use var_dump or dd in Laravel? Many of us also use logger to log output & figure out the problem in multiple steps. Spatie built a debugging tool called Ray that one can use to simplify the operation over dd or logger.

When in comes to Laravel packages, the guys at Spatie are probably the kings. They have hundreds of free packages you can pick from and use into your projects. Hats down for their commitment and contribution to this beautiful ecosystem.

In this article, we'll be using the Laravel Permission package from Spatie.

I'm thinking to make it as a software license, one-time payment with one year updates, as spatie.be do.

Ray by Spatie - Debugger tool

We use Oh Dear from spatie.be to check availability, dead links, certs and more for our critical FQDNs. Works perfectly fine. we also see it as a way to give something back to them in return for all their hard work in maintaining their open-source packages for Laravel.

The guys behind it work at Spatie[1] which you have probably heard of some of their packages, and Freek has a blog[2] that has a lot of PHP stuff on - lots Laravel, and lots just general new language stuff (covering PHP8 features etc)

[1] https://spatie.be

Spatie (https://spatie.be) makes a lot of great packages for Laravel. It also has a website with video courses and the code is open-sourced here https://github.com/spatie/spatie.be. I’ve learned a lot about testing from Spatie packages.

So I along with my colleague M H Hasib started working on a project of our own inspired from the API of laravel-permissions package by Spatie and the result was mongoose-permissions package.

Examples would be something like spatie.be, beyondco.de, and serversforhackers.com

[Credo](https://hex.pm/packages/credo) comes with a nice set of default checks and it is straightforward to add your own.

A static code analysis tool with a focus on code consistency and teaching. Config: {:credo, "~> 1.6"} Locked version: 1.6.3 Releases: 1.6.3, 1.6.2, 1.6.1, 1.6.0, 1.6.0-rc.1, 1.6.0-rc.0, 1.5.6, 1.5.5, ... Licenses: MIT Links: Changelog: https://github.com/rrrene/credo/blob/master/CHANGELOG.md <--- Here GitHub: https://github.com/rrrene/credo

[1] https://github.com/rrrene/credo/blob/master/lib/credo/check/...

I've already been thinking about more focus on teaching and explanations. Ruby gem strong_migrations and credo are good examples of communicating such knowledge to devs.

Yes there is a formatter built into Mix, the Elixir build tool. There is also https://github.com/rrrene/credo which is not as extensive but does the same thing as ESLint.