Hi, this is less of an issue and more of a suggestion for a quality of life improvement.
After the removal of the all() method from the FMEloquentBuilder (which as I realized totally makes sense) there is no longer a convenient way off circumventing the 100 record limit of the FM Data API.
This means you now have to write $query->limit(1000000000000000000)->get() (or similar) everywhere, or write your own helper method.
It would be nice if there was some helper provided by the package, or imo even better the get() method would automatically call ->limit(1000000000000000000) if no value was set prior to the get() call, as this better matches the behaviour of Laravel.
Of course you could also make this configurable to keep the default behaviour of the FM Data API as an option.
Yeah, I think we'll put this in as default behavior to set the limit to be very very high and bypass the regular 100. I was considering this after the last change.
Hi, this is less of an issue and more of a suggestion for a quality of life improvement.
After the removal of the
all()
method from theFMEloquentBuilder
(which as I realized totally makes sense) there is no longer a convenient way off circumventing the 100 record limit of the FM Data API. This means you now have to write$query->limit(1000000000000000000)->get()
(or similar) everywhere, or write your own helper method.It would be nice if there was some helper provided by the package, or imo even better the
get()
method would automatically call->limit(1000000000000000000)
if no value was set prior to theget()
call, as this better matches the behaviour of Laravel.Of course you could also make this configurable to keep the default behaviour of the FM Data API as an option.