fix: custom relationship meta not returned on PaginatedRelatedResourceResponse or PaginatedIdentifierResponse #23
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes a bug where currently custom meta added to a relationship via withMeta will not be returned on paginated relationship and related endpoints.
Steps to reproduce:
expected result: custom meta in the top level meta object
actual result: only pagination meta and any meta added directly to the response class will be shown.
have not added a test as there are no other response tests and this would be a fairly significant undertaking, perhaps it could be tested via proxy in the integration tests elsewhere?