Logs page for booking creation/edits/deletions

Open
#112 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
graphql, javascript, postgresql, react, typescript
Domain
backend-api-design, databases, full-stack

Research direction

No files, tests, or entry points are named. Start by tracing the booking creation, edit, and deletion flows and the existing P.R.I.T.-only page or access controls, then determine how event history can be stored and displayed. Done means all three event types are recorded, newest-first summaries are visible to P.R.I.T., and each entry shows the requested before-and-after details.

Written by the indexing model from the issue text.

Description

Currently, if a booking is changed or deleted there is no viewable record of what it previously was. Which is an issue if P.R.I.T. notices that no cleaning has been done afterwards, because you cannot see who made the booking.

As P.R.I.T., I would like the following features:

  • Logging of these types of events:
    • New booking
    • Edit to existing booking
    • Deleted booking
  • New tab/page viewable by P.R.I.T.
    • A chronological list of the logged events with newest first
      • The list should only be an overview, clicking the booking will show more detailed information
    • The following should be included in the list summary (for edits, the info after the change should be shown):
      • Type of event (create/edit/delete)
      • Who the booking belongs/belonged to
      • Committee
      • Title
      • Start and end days and times
    • The following should be included in the detailed information
      • Who the booking belongs/belonged to
      • Before and after of the following (no before for creations, no after for deletions):
        • Committee
        • Start and end
        • Rooms
        • Title
        • Description
        • Phone number
Dominant language
JavaScript
Stars
1
Forks
4
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cthit/bookIT-node

All issues in cthit/bookIT-node

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.