OmegaHawkeye
commented
3 weeks ago Definitely one of the biggest pain points right now, but I take it that Kirimase is meant to be a boilerplate tool. If it wanted to be a workflow tool that would be used throughout the development process, an evolution towards integrating with local LLMs would be necessary I think.
From kirimase created by briand1l: nicoalbanese/kirimase#150
Is your feature request related to a problem? Please describe. 'kirimase generate' works wonderfully to scaffold the MVC of something, e.g. Projects. The only problem is its all processed and written to the db, React components, etc, which then require manual edits to add or delete things to the data model or view. As an example if initially I decide that Projects requires a project_name, project_description and project_url, and then down the road I realize that I want a project_image_url for a cover photo, I have to re-do the entire process (it does gracefully overwrite mind you!).
Describe the solution you'd like If there were some persistence of the schema you just added with 'kirimase generate' (e.g. Projects) that the CLI would interpret and prompt to update instead of creating new, it would make this framework that much better. e.g. if I already created 'projects', ran the Prisma/Drizzle scripts but then wanted to add a 'project_image_url' to it. I suspect the problem with edit/update would become maintaining the View side, as it could be modified by the user manually.