You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The parameter order for `whereProperty` has changed to be consistent with Laravel conventions:
27
-
28
-
```php
29
-
// Old (v1.x) - DEPRECATED
30
-
User::whereProperty('age', 25, '>')->get();
31
-
32
-
// New (v2.x) - CORRECT
33
-
User::whereProperty('age', '>', 25)->get();
34
-
35
-
// For equality comparisons, both work:
36
-
User::whereProperty('status', 'active')->get(); // Still works
37
-
User::whereProperty('status', '=', 'active')->get(); // Also works
38
-
```
39
-
40
-
**Why this change was necessary:** The previous implementation had a critical bug where comparison operators gave inconsistent results because the system determined which database column to search based on the search value's type rather than the property definition's type. This caused queries like `whereProperty('level', '>', '3')` vs `whereProperty('level', '>', 3)` to search different columns and return different results.
41
-
42
-
**Migration:** Update all your `whereProperty` calls that use operators to put the operator before the value:
0 commit comments