Through my investigations with making a generic resource API, I have found prisma may be lacking in other required areas.
One of the biggest ones is the lack of modularity when it comes to table declaration and creation, which is a big part of how I want the library to work. I want to be able to have templates, as well as custom media tables, and all around modularity when it comes to the individual libraries.
However, Prisma requires pre-build declarations of tables, and these tables are all that can exist without a new build, which does not align with the end goal.
I will be investigating what to swap to, as I seem to have assumed too much about prisma when deciding on the architecture for this app. It's a good lesson in not assuming things when selecting pieces which will affect the whole project.
Through my investigations with making a generic resource API, I have found prisma may be lacking in other required areas.
One of the biggest ones is the lack of modularity when it comes to table declaration and creation, which is a big part of how I want the library to work. I want to be able to have templates, as well as custom media tables, and all around modularity when it comes to the individual libraries.
However, Prisma requires pre-build declarations of tables, and these tables are all that can exist without a new build, which does not align with the end goal.
I will be investigating what to swap to, as I seem to have assumed too much about prisma when deciding on the architecture for this app. It's a good lesson in not assuming things when selecting pieces which will affect the whole project.