Activity

[wavesinaroom]

Activities contain activities users get from the "boredb" database previously used in the log app. To edit an activity, users must search an activity that matches a chosen one from their log. To delete an activity on the other hand, users click the delete button.

Tasks

• [X] Routing
• [X] View
• [X] Template
• [X] Tests

Routing

• Requests are made to: planner/{day-date}/activities

View

Edit

• Activity fetch from the database
• Activities content replacement after choosing a activity from the database

Delete

• Remove activity in activities field

Template

• Provides a dynamic UI for editing or deleting results
• Renders activity results from the Log in a form (edit mode)

Tests

Edit

• Empty field changes to a new activity
• Activity changes to a different activity

Delete

• Field with a activity becomes empty

[wavesinaroom]

Activities field will actually have only one activity for the sake of simplicity

[wavesinaroom]

Changed my mind, I'm going back to the multiple activities field idea

[wavesinaroom]

Previous work on meals editing features help a lot develop this issue smoothly