Details
-
Umbrella
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
-
Stripes Force
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?
TestRail: Results
Attachments
Issue Links
- blocks
-
STCON-1 Peer components with different dataKey should store separate data
-
- Closed
-
-
UIIT-29 Newly created Item records should be in focus
-
- Closed
-
-
UIU-3 Display Records Found, Not Records Loaded
-
- Closed
-
-
UIU-95 Newly created user records should be in focus
-
- Closed
-
- relates to
-
FOLIO-671 Respond with descriptive information in consistent JSON on bad requests and server errors
-
- Closed
-
-
LIBAPP-177 Unsaved Changes Notification
-
- Closed
-
-
STRIPES-211 When a new record is created, the component should receive props describing it
-
- Closed
-
1.
|
Report errors in props.resources |
|
Closed | Jason Skomorowski |
|
|||||||||
2.
|
Add deprecation warning for props.data |
|
Closed | Unassigned | ||||||||||
3.
|
Remove props.data, have only one reducer for RESTResource |
|
Closed | Jason Skomorowski |