Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

status (and error, warn?) props for connected components

Description

OkapiResource (and RestResource) can expose information from their HTTP responses by including an additional prop to connected components: status with keys for each resource.

In addition to providing the response once available, it can indicate a response is still pending or has timed out. In order to highlight unusual status we could also provide error warn

For the mutators, I believe we pass through the promise from fetch, is that sufficient?

Environment

None

Potential Workaround

None
100% Done

Checklist

hide

TestRail: Results

Activity

Show:

Mike Taylor July 15, 2017 at 12:38 AM

Makes sense to me.

Jason Skomorowski July 15, 2017 at 12:37 AM

links still work

And re: closing, I was going to leave this open pending the rest of the implementation (pendingMutations/failesMutations). But I've also made issues for those now as they are distinct enough so, while I like this as an umbrella, it still works well for that if it's closed.

Mike Taylor July 15, 2017 at 12:07 AM

Now you've moved this issue from to , are you going to rename all the actions and reducers that have "111" at the end of their names?

Mike Taylor July 4, 2017 at 10:36 PM

I say again: we should close this as DONE, and file any refinements as their own issues.

Mike Taylor June 16, 2017 at 10:04 AM

I think you should close this issue as DONE, and file one or more new ones for the refinements.

Done

Details

Assignee

Reporter

Labels

Priority

Development Team

Stripes Force

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created December 10, 2016 at 12:35 AM
Updated May 23, 2019 at 3:25 PM
Resolved May 23, 2019 at 3:25 PM
Configure
TestRail: Cases
TestRail: Runs