macropay-solutions

We solved this issue more than 3 years ago with: https://github.com/macropay-solutions/laravel-crud-wizard-free/blob/e6a9bb60ba28e644bb1cf5c5979e0c6b267fca20/src/Providers/CrudProvider.php#L24 It does not cause problems.

Sorry for the previous replies. Now we understood the real issue. This is called ```php $user->categories->pluck('id') ``` while the ```php static::$constraints ``` is false because of the eager load of...

@Tofandel @allandantasdev If the Relation had this function(which is doable via macros as static function): ```php /** * Run a callback with constraints enabled on the relation. * * @param...

UPDATE: https://github.com/laravel/framework/issues/51825#issuecomment-2419387066

@Tofandel Your code always set static:$constraints = true; https://github.com/laravel/framework/issues/51825#issuecomment-2179431011 Our suggestion sets it only once (with the previous value not with hard codded true) at the construct's end and not...

@marius-mcp Good catch. Then the whole Relation::noConstraints logic from \Illuminate\Database\Eloquent\Builder::getRelation is not fitting in...

**PROPOSED SOLUTION** @Tofandel Another solution that sadly can't be implemented via macros for older versions: \Illuminate\Database\Eloquent\Relations\Relation UPDATED the Relation construct **(and all its children's constructs to pass down the resourceModel).**...

FYI We will not be issuing a merge request or pull request with this solution. We shared the solution to help the community but only if the community wants to...

@taylorotwell do you see any uncovered situations by this solution https://github.com/laravel/framework/issues/51825#issuecomment-2419387066 ?

@Tofandel We respect your point of view, as you should also respect ours. We spent 2 days (also not paid, and we are a team not just a dev) figuring...