linting should prompt for an action on upcoming unreplied-to events ("needsAction")

[flavorjones]

Related Issues

• [ ] #59
• [ ] #60

[mikfreedman]

is this the first linting story @flavorjones ?

[flavorjones]

yes, I tried to put the "to do" backlog into a nice order. feel free to grab something else if you want but I think this is good to do first because:

• linting is contained to examining the event (and not something more complicated like "this meeting conflicts with another meeting" or "hours of meetings in this day")
• the update action is a chance to flesh out some of the behaviors around responding to a meeting, including
  • yes/no/maybe UX
  • send notifications? (I think we should default to yes for now)
  • testing how the EventRepository feels for a simple update like this

[flavorjones]

Here's what I had in my head for UX:

$ calendar-assistant lint today
[email protected]

An Event is awaiting your response:

  2018-10-01  10:30 - 10:55 | Facilitate out-of-the-box deliverables (1:1, recurring)
  Attendees:
  • [email protected] (accepted)
  • [email protected] (maybe)
  • [email protected] (declined)
  • [email protected] (awaiting)

Response? (Skip / accept / maybe / decline) > a

  Accepting Facilitate out-of-the-box deliverables (1:1, recurring) ...


An Event is awaiting your response:

  2018-10-01  11:00 - 11:30 | Syndicate plug-and-play systems (recurring)
  Attendees:
  • [email protected] (accepted)
  • [email protected] (maybe)
  • [email protected] (declined)
  • [email protected] (awaiting)

Response? (Skip / accept / maybe / decline) > hit return for default

  Skipping Syndicate plug-and-play systems (recurring) for now.


An Event is awaiting your response:

  2018-10-01  11:30 - 12:00 | Facilitate bricks-and-clicks methodologies (1:1, recurring)
  • [email protected] (accepted)
  • [email protected] (maybe)
  • [email protected] (declined)
  • [email protected] (awaiting)

Response? (Skip / accept / maybe / decline) > s

  Declining Facilitate out-of-the-box deliverables (1:1, recurring) ...


No other events require your attention. Have a great day!

[flavorjones]

So yeah, maybe we should break this down into smaller stories, similar to how I've done it in #18 having multiple stories link back to it?

[mikfreedman]

Ar the very least I think there’s a read only story that can go first

On Mon, Dec 10, 2018 at 16:12 Mike Dalessio [email protected] wrote:

So yeah, maybe we should break this down into smaller stories, similar to how I've done it in #18 https://github.com/flavorjones/calendar-assistant/issues/18 having multiple stories link back to it?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/flavorjones/calendar-assistant/issues/9#issuecomment-445974978, or mute the thread https://github.com/notifications/unsubscribe-auth/ABH0QJSQXystGM1Lg9RJ3Q_Kl7A6H815ks5u3s4ygaJpZM4Wq0jY .