Creating Resources tab for GUI Editor
MoSCoW Requirements Checklist
Must-Have
-
Ability to create a new resource schema with customizable fields (array, boolean, integer, object, number, string, relation) -
Adjustable field properties (Max length, Min length, required, positives, format, cascading) -
Manage resource properties (Expiring resources, clonable, ephemeral, seeded) -
Define resource security roles -
Edit and delete existing resource schema with data loss warning -
Overview of created resources -
Add, update, and delete records manually -
Express changes in appsemble YAML -
Visualize YAML correctly
Should-Have
-
Guided wizard for user assistance -
External resources' resource property -
Visualize relationships between resources with an ERD -
Clickable visualization for easy navigation to editing page
Could-Have
-
Draggable and rearrangeable ERD visualization -
Selective resource visualization -
Support for various resource relationships (will require a look into current Appsemble YAML working) -
Customize resource record view (hide/show columns)
Would-Have
-
Ability to upload existing database schema
Fine-Tuning
-
The resource overview doesn't have error handling on why it's unable to add a record if the added record doesn't satisfy some condition. Ex. greater int than maximum is defined. -
Should add validation to prevent users from inputting existing resource names into new resources and duplicate field names -
Making the new resource form a modal could potentially help with user experience. -
Existing fields lack defining some options. Ex. regex for strings or triggers for relationships. -
Array field type isn't implemented yet. -
In the overview, as viewed from the GUI, the API button doesn't work. -
Enums aren't supported yet
New Wireframes: #1422 (comment 1827451403)
Previouse Wireframes: #757 (comment 1123588514)
Edited by Marcin Marcinkiewicz