feat(meta): Passes meta to result description functions [#1904] #1910
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 20fd4d8:
|
|
Seems reasonable. Thanks! |
|
Thanks @markerikson . I'll put together a second PR for docs changes in the next couple of days. |
phryneas
reviewed
Jan 13, 2022
| @@ -513,6 +513,7 @@ export function calculateProvidedByThunk( | |||
| isFulfilled(action) ? action.payload : undefined, | |||
| isRejectedWithValue(action) ? action.payload : undefined, | |||
| action.meta.arg.originalArgs, | |||
| action.meta, | |||
There was a problem hiding this comment.
Sorry for chiming in late, but I'm like 80% sure that this is the "wrong meta".
I'm pretty sure this would need to be action.meta.baseQueryMeta.
Can you please verify this?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The internal and public interfaces for result descriptions are getting a little spread out, but I didn't see an easy solution to simplify the result description callback interface without a breaking change. This seems perfectly functional and passes tests. I didn't see any existing testing for
calculateProvidedBy, so I didn't try to take that on.After feedback, I will be glad to update the corresponding docs.
References #1904