Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Server/Data Service Generator]: [Add an ability to import or write schema.prisma to amplication] #1617

Open
sandbox-apps opened this issue Jul 16, 2021 · 7 comments

Comments

@sandbox-apps
Copy link

Is your feature request related to a problem? Please describe.
I love how good Amplication is using the UI for creating model/entity.
But really the easiness and the joy writing a schema using Prisma DSL sometimes makes a lot more sense and faster than specifying all by clicking and selecting, connecting types in the form...

Describe the solution you'd like
Add a feature where we can add a schema.prisma file or directly write a schema.prisma file inside amplicationn much like a prisma playground and generate all the entities base on the prisma file

@sandbox-apps
Copy link
Author

Maybe if we can also build things like this all other things like this issue can be solve at least without the UI Form
#1493

@yuval-hazaz
Copy link
Member

Thanks! that is a good idea and it can be very helpful also to cover all use cases which are not yet supported by the UI or CLI

@all-contributors please add @sandbox-apps for ideas

@allcontributors
Copy link
Contributor

@yuval-hazaz

I've put up a pull request to add @sandbox-apps! 🎉

@sandbox-apps
Copy link
Author

Yeah after all Prisma will have much more new features coming out. Like specifying also triggers and constraint in the schema.. Also. maybe a creating a virtual table view in near future. :)

@yuval-hazaz
Copy link
Member

agree

@sandbox-apps
Copy link
Author

By this if will be implemented, we can also have the cascading option on specifying models that I believe is not yet available in the UI?

@yuval-hazaz
Copy link
Member

That is correct, cascade is not available yet.
see #1409

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Candidate
Development

No branches or pull requests

2 participants