add support for async RSAA properties #235
Merged
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.
When defining an RSAA action, you can define the properties of the RSAA action (body, headers, options) to be either a plain JavaScript object or a function.
If a function, the middleware executes the function to attain the result. The middleware that is executing the function is already an
async
function, so I added anawait
before the call of the above RSAA properties, so that async functions could be passed in and still evaluated.To give a real-world example of why this is necessary: I store credentials for an API on the keychain in React-Native. I set the headers property to be a function that reads the keychain and formats the Authorization header. Accessing the keychain is done asynchronously. This change allows an async function to be used, and does not affect synchronous functions.