[LARP DB] Schema for generating lists of characters for pre-reg that are individualized for each LARP is looking good.

[LARP DB] Crated the new tables in the system for a pre-reg setup... and the fact that I think I can slap this together end-to-end really fast is kinda scary.

[LARP DB] Okay, DEFINITELY stepping back now. Why is it I keep wanting to see the next step with what the new system can do?

At this point I've got two UI/UX choices to drill down on and I really need that answer before I forge ahead.

[LARP DB] To give an example of what I've been doing in the last week.

Note, both of these examples are running with the same backend and same DB:

Before:2023-12-17_00-29-32
After:2023-12-17_00-25-56

Okay I think that's enough project work. I've got like a 1/4th of the thing set up in the new framework and I've got all I need to know about how to access and mess with the data via the front end.

I'm just about at the point I could call myself a React developer.

[LARP DB] Definitely a learning curve to use the new framework tools like React Query, but the utter zippyness for the upgraded app is undeniable.

[LARP DB] - Here's a weird question. For user permissions, should you be able to lower or remove your permissions?? Like should you be able to just remove yourself from the system if you wanted? Of course you can't change anyone else without already having permissions to do so but, what level of security do we want?

[LARP DB] Note to self, standard practice with APIs is to always send back a 200 on success with some body data, modern front end packages kinda depend on it to know what's what. ^.^;

[Pol] Rudy Giuliani now owes $148 MILLION to Georgia election workers he defamed.

In a move that's exceedingly on brand for me, I won a Christmas trivia contest at work.