Surface status code in state

[generalpiston]

Status codes are useful for front end state management. For example, an API that return 403 and 401 can be treated differently. Also, sometimes APIs return 202 for async processing.

[generalpiston]

Here's an example: generalpiston@b8e3f57.

[generalpiston]

Added PR: #320

[rstire364]

Is there any concern about the implications of this change with non-request async functions?

[generalpiston]

@rstire364 great point. I didn't think about it. Would it make sense to make it optional?

[rstire364]

This might not be a popular answer but I think it's a user-land issue. I would argue this change borders on a violation of separation of concerns. React Async is concerned with providing an abstraction around async state management.

To be fair, I've used React Async exclusively with Axios, so status and statusCode are readily available. This further reinforces my thought that this is a request library responsibility and not React Async's.

[generalpiston]

To your point @rstire364 . I could have also just made accept another value as well.

[rstire364]

Certainly a valid

[generalpiston]

Let's close this then. Thanks @rstire364