Details
-
Bug
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Duplicate
-
None
-
None
Description
At present, the data that stripes-connect loads from an Okapi resource (or any RESTful web-service) is stored in an area named after the resource, scoped within the UI module. But a module contains many components, and components may have many instances. So the resource's data should be scoped to the component instance, not the module (nor the component class).
TestRail: Results
Attachments
Issue Links
- blocks
-
STRIPES-293 Make a proof-of-concept joining component
-
- Closed
-
-
UIORG-18 Edit preferences for multiple plugins
-
- Closed
-
-
UIU-104 Select User Proxy v1
-
- Closed
-
- duplicates
-
STCON-1 Peer components with different dataKey should store separate data
-
- Closed
-
-
STRIPES-265 Instantiate resource objects per-instance... somehow?
-
- Closed
-
- is blocked by
-
STCON-15 Replace redux-crud with our own actions and reducers.
-
- Closed
-
- relates to
-
STRIPES-211 When a new record is created, the component should receive props describing it
-
- Closed
-
-
UICHKOUT-7 Search and Select User on Check-Out Screen
-
- Closed
-