So, we got the sign up and log in routes.
We of course also need some routes for registering events, editing events and so on.
Now here I now switched to Visual Studio Code with GitHub Copilot simply so that I can show
you both.
Obviously I would typically stick to one of the tools, either use cursor or Visual Studio
Code with GitHub Copilot, but for this course I want to show you both, so that's why I switched.
And as a next step I want to add more routes here, some event specific routes.
Hence I'll add an events.js file in the routes folder.
And then of course here, with GitHub Copilot enabled, I can also of course open the chat
and ask questions here or do it in line in a file, like here in events.js, where I can
ask Copilot to add some event specific routes which can be used to create events, edit an
event, identified by ID or delete an event.
Use ESM imports exports.
I'm adding this here since I switched and I'm not sure if it's aware of the general
import export style I'm using in other files.
Now with that, let's see what I'll get here, if that's enough for it.
Yeah, it's okay.
I'll accept it, but I'll need to tweak it.
The import looks good, that looks good, that of course makes no sense.
We have a database, but GitHub Copilot doesn't know here because I'm just in this one file.
It doesn't have knowledge about the other files here, at least at the point of time
where I'm recording this with this inline chat.
In this chat here, I could have added my workspace as a reference to make it aware
of it, but in the inline and in file chat right now, it's not aware of the entire code
base.
So I didn't know about that.
Hence, I'll remove this part here and simplify those routes so that it's really just extracting
event data and then we'll have to do something with that.
All this code here where it tries to read some event and so on, all that actually can
and should be removed here.
So that's what I'll do here real quick, like this.
Now actually, we can also delete this here.
We'll need to add more code here later.