Week 6: Michelle and Ethan ("As a user, I want to view a list of my shopping list items in order of how soon I am likely to need to buy each of them again")

AC:

• Items in the list are shown grouped in the following order: Soon, Kind of soon, Not soon, Inactive
• Within each grouping, items should be sorted by the estimated number of days until next purchase
• Items with the same number of estimated days until next purchase should be sorted alphabetically
• Items in the different states should be visually distinct
• Items in the different states should be described distinctly when read by a screen reader

Possible States:

Possible item states are as follows:

• Need to buy Soon (fewer than 7 days)
• Need to buy Kind of soon (between 7 & 30 days)
• Need to buy Not soon (more than 30 days)
• Inactive (only 1 purchase in the database or the purchase is really out of date [2x the estimate?])

Initial Notes:

• Created branch and wiki page. Agreed to start work independently and collaborate on a Zoom call on 12-18-19
• Branch is named "mm-eb-ordered-list"
• Q: Story says "...view a list of shopping items...". Should we simply organize the primary list view, or create other views with differently organized lists?
• Q: Does the example app employ this week's AC? I don't think so...looks like we will be striking out on our own.
• How can we make sure we maintain accessibility? Can we use aria labels that are generated by class?
• Use numberOfDays from the db as the standard to sort items. Write conditionals that place li items in different lists depending that value?
• Second call on 12-21-19 to continue working on AC, as well as final call on 12-22-19 for the teams to merge the code and deal with conflicts.