While workling on the integration to the frontend, I found a few issues on the backend:
/app/api/songbooks/route.ts POST: requiers language althought it shouldn't (and the description tells it wouldn't). In general the descriptions are sometimes wrong (e. g. telling the API requires "name" althought it's "title")
many (e. g. /lib/db/song.ts): variables are type of 'unknown'.
many (e. g. /app/api/songbooks/[songBookId]/songs/[songId]/route.ts): params have a 'any' type.
/app/api/songs/route.ts POST: why does the description speak about songbooks althought the API handles songs (hopefully)??
Should I fix them or will you? There might come some more issues in some time.
While workling on the integration to the frontend, I found a few issues on the backend:
- [ ] /app/api/songbooks/route.ts POST: requiers language althought it shouldn't (and the description tells it wouldn't). In general the descriptions are sometimes wrong (e. g. telling the API requires "name" althought it's "title")
- [ ] many (e. g. /lib/db/song.ts): variables are type of 'unknown'.
- [ ] many (e. g. /app/api/songbooks/[songBookId]/songs/[songId]/route.ts): params have a 'any' type.
- [ ] /app/api/songs/route.ts POST: why does the description speak about songbooks althought the API handles songs (hopefully)??
Should I fix them or will you? There might come some more issues in some time.
I forgot to say, that i've done many of Copy and paste, so there could be some issues. The code should work fine, because i usually check the variables in the /lib/-APIs.
You can just ask AI how the Description should be...
I forgot to say, that i've done many of Copy and paste, so there could be some issues. The code should work fine, because i usually check the variables in the /lib/-APIs.
You can just ask AI how the Description should be...
I forgot to say, that i've done many of Copy and paste, so there could be some issues. The code should work fine, because i usually check the variables in the /lib/-APIs.
You can just ask AI how the Description should be...
I mean for the wiki...
> I forgot to say, that i've done many of Copy and paste, so there could be some issues. The code should work fine, because i usually check the variables in the /lib/-APIs.
>
> You can just ask AI how the Description should be...
>
I mean for the wiki...
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Migrate to prisma from better-sqlite3
[refactor] migrate to prismato refactor: migrate to prismaDas Grundgerüst ist gemacht, ich kann mit dem ORM (primsa) arbeiten (funktionen aufrufen, usw)
TODO: Umarbeitung von @/lib/db*
Function to the Database and the API are done. Now only the Frontend is todo.
While workling on the integration to the frontend, I found a few issues on the backend:
Should I fix them or will you? There might come some more issues in some time.
I forgot to say, that i've done many of Copy and paste, so there could be some issues. The code should work fine, because i usually check the variables in the /lib/-APIs.
You can just ask AI how the Description should be...
Functions not implemented yet (but needed):
I mean for the wiki...
What do you mean for the wiki