laravel-mysql-spatial VS laravel-enum

I think laravel-mysql-spatial is worth mentioning in this context.

just go to the issues in the repository, and actually look at them https://github.com/grimzy/laravel-mysql-spatial/issues .

You should definitely check out https://github.com/grimzy/laravel-mysql-spatial.

Like /u/octarino said, do the distance filtering in the database. If you're using MySQL, give this package a try: https://github.com/grimzy/laravel-mysql-spatial. Just add a trait to the model, and you get some really useful query scopes. Or you could use the ST_DISTANCE_SPHERE() function manually in a raw where clause. The only requirement is that the location is stored i a column of type POINT (the package also makes it easy to create these in migrations).

Suppose we have a Permission enum in our Laravel project, and when an admin assigns a permission to a user, we need to verify if the permission is valid. To accomplish this, we'll create the Permission enum using BenSampo/laravel-enum package:

About Laravel Enum

I use this laravel-enum package, Spatie has one that I'm sure is great as well. Have you checked out how they do things to see if there are any takeaways? They're a different approach because the list of enums aren't stored in the database, which I really like because it means I can get the enum types and values autocompleted in my IDE. There are also some convenient features like attribute casting and validation rules.