Creating records should create all sub-records

Description

As documented in STRIPES-139, a skeletal record – such as one in which only the username is set – can cause problems downstream. I will make the Users UI module's display code robust against such problems, but I think that – belt and braces – the record creation code should also ensure that all subrecords are included in the POSTed record, even if they are empty.

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Jason SkomorowskiJune 14, 2019 at 2:04 PM

Sounds ultimately like a backend issue at the core of the data model: data integrity. Which we know is a fair challenge that we took on by splitting data across services rather than relying on a single database and many people have been hard at work on compromises for a while now. I'm closing this issue because it doesn't seem to add much and has been around for a while--the Stripes end of things is mainly to be graceful when things are incomplete while surfacing an error so there is an opportunity to notice potential corruption. And I think the more specific detail about the user creation form has long been accounted for.

Mike TaylorJanuary 17, 2017 at 2:20 PM

That's fine – I already did , so there is no great urgency to this. Mostly I want it in the back of our minds as we think about other edit-related stuff.

Niels Erik NielsenJanuary 17, 2017 at 2:16 PM

This immediately sounds like a semi-big change of the standard mode of operation for redux-form, we should maybe consider it a bit.

Done

Details

Assignee

Reporter

Priority

Development Team

Stripes Force

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created January 17, 2017 at 1:04 PM
Updated June 14, 2019 at 2:04 PM
Resolved June 14, 2019 at 2:04 PM
TestRail: Cases
TestRail: Runs