imanghafoori1 / eloquent-relativity

Allows you to decouple your eloquent models from one another.

Hi, I am Iman 👋

You can hire me:

My Github Stats:

Since September 2020

I have a handful of Laravel packages:

Debug Assistant:

• Laravel Microscope (Smart bug finder and fixer)

Design pattern:

• Laravel Widgetize (Page Partial Caching)
• Laravel Heyman (Declarative programming in laravel)
• Laravel Terminator (Tell don't ask in laravel)
• Laravel Decorator (Decorator pattern in laravel)
• Laravel Nullable
• Laravel Middlewarize (Decorate your method calls using pipelines)
• Laravel Smart Facades (More features on the top of the facades)
• Smart Real-time Facades (IDE Auto-completion for real-time facades)

Auth Stuff:

• Laravel Master Password (Securely Login with Master Password)
• Laravel Any Password (Allows you to login with any password on local environment)
• Laravel Password History (Force users to reset to a never used password like Gmail does)
• Laravel Tokenize Login (Passwordless Login)

Testing:

• Eloquent Mockery (Adds the missing "php array" driver to the Eloquent)

Eloquent:

• Laravel Temp Tag (Tag Any Eloquent Model Instance)
• Eloquent History (Keep track of your eloquent model changes)

Utility:

• Laravel Video (Stream Videos in Laravel)
• Laravel File Cache Cleaner (Clean-up expired cached items in filesystem)
• Composer Json Reader (Read from composer.json file easily)

My contributions to laravel/framework:

• My Merged PRs on laravel/framework

and that is all...

eloquent-relativity's Issues

Suggestion: camelCase methods

Hi, this is a simple suggestion, but why the methods are not following the standard PSR-1?
Method names MUST be declared in camelCase.

I understand that there are already methods called like morphMany, so this is, i guess, the reason why you choose to use morph_many, but wouldn't fell more natural and readable to use methods like
attachMorphMany or addMorphMany or dynamicMorphMany?

Is it useful for latest Laravel 7 update?

laravel/framework#33025

header image

This package does not work when i use l5-repository

hi Mr. Ghafouri

i install this package in my project , but does not work Because i use l5-repository package

when

php artisan serve

get error when i use DynamicRelations in PostRepository :

Call to undefined method Prettus\Repository\Eloquent\BaseRepository::__call()

get error when i use DynamicRelations in BaseRepository:

Cannot access parent:: when current class scope has no parent

Is it possible to guide me about this? (tnx)

Trait free

Hi, great package!

Is there any chance to make this package trait free?

Relationships mapper

Hi, currently to map all relationships added i'm using this:

use Illuminate\Support\Collection;
use ReflectionClass;
use App\Models\Foo;

$model = Foo::class;
$class = new ReflectionClass($model);
$property = $class->getProperty('dynamicRelations');
$property->setAccessible(true);
$methods = array_keys($property->getValue('dynamicRelations'));

Is there a way to do this without reflection?
Maybe adding an interface and a public method getDynamicRelations()

Thanks

L8?

Thank you for this, and your other packages. They are quite helpful for decoupling. Will this be updated to L8? It's basic dependency updates, really I'm curious if this package is maintained anymore.

Thanks for the great work. Much appreciated.

Conditional relationships

What should be the best approach to attach relationships based on a condition of the given entity if the class is the same?

For example:

• attach relationship detail to all entities Book that have an attribute type=foo
• attach relationship friends to entity BasicEntity that have table value cats

I'm asking this because i have one single Model that in each instance may have different table values because these models are defined in the database and there is only one class.

Can i make a PR about this or should i simple create an addon/extension?