nexplan-backend-python/notes.txt at main · SimpleOutput/nexplan-backend-python · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
TODO:

Connect create_event() in events.py to prompt grabber script


update_event()
--- use delete_event and create_event for updated event
--- prompt needed to update reschedule (date/time) / rename (event name) / all-day (how does all-day look)

delete_event() (will need a x button on front end to trigger)
x button passes : uuid for deletion to backend
confirmation yes to delete (delete "title" task?)

home page explaining the project

Add support sectoin (prompt to send email)?

about section

-----
If tables don't exist just run postgres server and DBs will be generated:
Two dbs

table - users
id: unique per data base entry
clerk_id: unique per user (set thru createUser func)
email: clerk email
created_at:

table - events
id: Primary key
user_clerk_id
event_title: string (name of event)
event_description: string (descrption / notes for event)
event_date
all_day: true/false (required)
start_time: optional
end_time: optional
created_at: time first set in createTask
updated_at: updateEvent (TBI)
-----

errors?
When not enough information
(time, date, even title, occurences?, )

When same event name used

Update event even needed?

Conflicting time of events / two tasks overlap


CreateEvent() - (generate_uuid(),
user_id , event title, date, all_day - if FALSE (start_time, end_time))
user_id, event_title, date, all_day (if FALSE start_time, end_time)
testing string: "hackathon 06/02 all_day"
Then after the fake data of testing front end to the back end I can attempt the database


----
Examples manually query on PGAdmin used for testing get_Events()
## Change user to user_id in users DB

INSERT INTO events (id, user_id, title, date, all_day, start_time, end_time)
VALUES (
    '1f7d9a3b-2d98-4c9e-93c7-7dbeed59d208',
    'user',
    'Weekly Planning Meeting',
    '2025-05-27',
    FALSE,
    '2025-05-27 10:00:00',
    '2025-05-27 11:00:00'
);

INSERT INTO events (id, user_id, title, date, all_day, start_time, end_time)
VALUES (
    'd0c9e1e2-0b4f-4bfc-83f9-4f2a7ecbe0cb',
    'user',
    'All-Day Conference',
    '2025-06-01',
    TRUE,
    NULL,
    NULL
);

INSERT INTO events (id, user_id, title, date, all_day, start_time, end_time)
VALUES (
    '5c53bba4-46f4-4d2b-bd65-68ab4c62dc10',
    'user',
    'Code Review Session',
    '2025-05-29',
    FALSE,
    '2025-05-29 13:30:00',
    '2025-05-29 14:30:00'
);

INSERT INTO events (id, user_id, title, date, all_day, start_time, end_time)
VALUES (
    'b16af487-cfad-44aa-bb8b-69a5c174e3b6',
    'user',
    'Hackathon Kickoff',
    '2025-05-31',
    FALSE,
    '2025-05-31 09:00:00',
    '2025-05-31 12:00:00'
);

INSERT INTO events (id, user_id, title, date, all_day, start_time, end_time)
VALUES (
    '8f5c62d2-12e9-4d20-bb6c-8e4c56de1d43',
    'user',
    'Mock Task 1',
    '2025-05-22',
    FALSE,
    '2025-05-22 09:00:00',
    '2025-05-22 10:00:00'
);

INSERT INTO events (id, user_id, title, date, all_day, start_time, end_time)
VALUES (
    'f72ae20d-35a3-4cb4-a5fc-d92f3a7b02ec',
    'user',
    'Mock Task 2',
    '2025-05-23',
    FALSE,
    '2025-05-23 14:00:00',
    '2025-05-23 15:00:00'
);