Skip to content

fix(schema): result resolver correctly resolves paginated find result#2594

Merged
daffl merged 2 commits intofeathersjs:dovefrom
idaho:fix-result-resolver
Apr 11, 2022
Merged

fix(schema): result resolver correctly resolves paginated find result#2594
daffl merged 2 commits intofeathersjs:dovefrom
idaho:fix-result-resolver

Conversation

@idaho
Copy link
Copy Markdown
Contributor

@idaho idaho commented Apr 7, 2022

Summary

This pull request will resolves an issue with the resultResolver in combination with a paginated services.

Currently the schema resultResolver resolves the result on context.data. This will end up in an issue if you have a service configured with pagination enabled.

Before the resultResolver is running we have the properties total, limit, skip and data on context.result. After all properties are resolved, the result of it will set to context.result. That means, that the paginated result structure gets los.

@daffl daffl merged commit 6511e45 into feathersjs:dove Apr 11, 2022
@daffl
Copy link
Copy Markdown
Member

daffl commented Apr 11, 2022

Great, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants