Alert management process - Githubissues

keithamoss / hansardalerts

@HansardAlerts for Western Australia's Hansard

MIT License

2 stars 0 forks source link

Alert management process #10

Open keithamoss opened 10 years ago

keithamoss commented 10 years ago

Depends on issue #9.

Users can see all of their current alerts on the index page. The table might be rendered with ngTable.

Search text
Leg. Assembly
Leg. Council
Status (Off/On)
Creation date - Do they care?
{Enable|Disable}/Delete/Edit buttons

{Enable|Disable}:

Display confirmation dialog? Who cares?
PUT to /api/alerts/{id}/{enable|disable}
Change status in Angular-land, hopefully magic data binding updates the table
Display confirmation of action completion - row colour fades to default? Toastr?

Delete:

Display confirmation dialog
DELETE to /api/alerts/{id}
Flag as deleted in DB
Remove from data in Angular-land
Display confirmation of action completion - whatever we did for alert creation (Alerts / Toastr)

Edit:

In-table edit vs modal edit. Whatever ngTable works nicest with (to start with, at least)
Edit button should become 'submit'-esque button
PUT to /api/alerts/{id}
Either return confirmation from API or let angular re-request from GET /api/alerts/{id} and update magically.
Display confirmation of action completion - whatever we did for alert creation (Alerts / Toastr)