Please review and provide feedback

[heratyian]

@DPI-WE/technical-associates

[thierrychau]

• What do you think of separating both nested routes and nested attributes? It could be confusing to have both together, since they are different concepts with different uses.
• I like the example for nested routes and giving all the routes generated!
• I like having an example for the nested attributes too. Is this the right place to mention also that for mass params, the arrays need to be the last arguments?
• to do(?): what are your thoughts on adding a more "complex" example? my major struggles were with dealing with the edit action (pre-populating existing nested attributes - deleting and creating the nested attributes upon update) ; and also dealing with multiple instances (multi select in the form)

[heratyian]

What do you think of separating both nested routes and nested attributes? It could be confusing to have both together, since they are different concepts with different uses.

I think you're right. Right now I have it in the RCAV module. (sprint 1) It makes sense to keep nested routes in the RCAV module. Maybe move nested_attributes to the Object Relational Mapping (ORM), Rich Domain Models, and CRUD module?

[heratyian]

I like having an example for the nested attributes too. Is this the right place to mention also that for mass params, the arrays need to be the last arguments?

this would be a good aside note