Timeline for REST API design for web pages with wizards
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 11, 2016 at 4:37 | comment | added | Chris Cirefice | @TechCrunch Basically Guillaume means that the object/table representing the form can be broken into parts, where part of the model is saved at each step. In fact, you can just have each "step" be a form for part of the entire model. And if you take this approach, it actually makes the architecture incredibly simple. Each POST to the server will (create or) update the same model, and each GET will load the same model, and each step will be a form to fill in sets of fields that are semantically meaningful (belong together). And simply have a boolean on the model for in_progress or draft. | |
| Feb 10, 2016 at 21:37 | comment | added | guillaume31 | You're welcome. By the way, the "two table" approach isn't mutually exclusive with this. Having one HTTP resource per step doesn't dictate your object model on the application server, let alone the database schema. It's just a Web representation. | |
| Feb 10, 2016 at 16:18 | comment | added | TechCrunch | I'm am using Angular for the UI. So I'm not sure how much helpful the state machine is. But I think step based resource seems to be more meaningful than managing another table. Also, I should be able to submit everything in a single step. Will give it a shot on this design today. Thanks for the help. | |
| Feb 10, 2016 at 13:32 | history | edited | guillaume31 | CC BY-SA 3.0 | added 3 characters in body |
| Feb 10, 2016 at 12:46 | history | answered | guillaume31 | CC BY-SA 3.0 |