Difference between revisions of "Designate/Blueprints/Recordset Record API Redesign"
< Designate | Blueprints
(→Overview) |
(→Overview) |
||
Line 15: | Line 15: | ||
|} | |} | ||
− | This blueprint proposes to | + | This blueprint proposes to eliminate the Records resource and on keep the RecordSets resource. |
− | + | The API for recordsets and records is too complicated. Currently, a user is forced to create a recordset before creating a record. This leads to a confusing user experience.Users will create, update and delete recordsets. When the user creates a recordset the code will determine if it should be a new recordset or a record under an existing recordset. | |
− | |||
− | |||
− | |||
− |
Revision as of 19:01, 29 April 2014
Contents
1 Overview
Overview
Gerrit Patch | [] |
---|---|
Launchpad Blueprint | [1] |
This blueprint proposes to eliminate the Records resource and on keep the RecordSets resource.
The API for recordsets and records is too complicated. Currently, a user is forced to create a recordset before creating a record. This leads to a confusing user experience.Users will create, update and delete recordsets. When the user creates a recordset the code will determine if it should be a new recordset or a record under an existing recordset.