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
Now, convert the results to other structs/public responses is not posible, for example, a common case is the User model which have sensitive data like password, confirmation token, even more, but that fields can't be returned in the response, so we need to create a PublicUser struct to exclude that fields
Feature Description
Maybe a solution is to pass some kind of transform closure which can be used in the pagination process
The text was updated successfully, but these errors were encountered:
I've been out of town for a while and haven't had much time to work on doing something like that. Originally I wanted to do something that conformed to a protocol and would allow easy transformation. My goal is still that, however, I haven't given it much thought to work on it since I've just been swamped. I'll be home in a couple of weeks and will be able to start thinking about some ideas again.
Motivation Behind Feature
Now, convert the results to other structs/public responses is not posible, for example, a common case is the
User
model which have sensitive data like password, confirmation token, even more, but that fields can't be returned in the response, so we need to create aPublicUser
struct to exclude that fieldsFeature Description
Maybe a solution is to pass some kind of transform closure which can be used in the pagination process
The text was updated successfully, but these errors were encountered: