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

Validator idea #9

Closed
bpocallaghan opened this issue May 16, 2017 · 2 comments
Closed

Validator idea #9

bpocallaghan opened this issue May 16, 2017 · 2 comments

Comments

@bpocallaghan
Copy link
Owner

Validator idea...
Also, I never run the migration at the time of generate:resource since there are only a few things that are common, the rest gets built, then the migration is performed. Once performed, it would be great to do some like:

generate:validator foo_bar

And then using Doctrine/dbal we could get the schema and inject the proper validator in the store and update of the FooBarController (at least all of the required fields.)

@maddeezy
Copy link

Second thought...we don't need doctrine at all, just read the Laravel migration.

Then we can determine all unique, non-nullable, and number of characters, etc as defined by the migration.

@maddeezy
Copy link

Although doctrine would be better suited for apps already deployed.

@bpocallaghan bpocallaghan closed this as not planned Won't fix, can't repro, duplicate, stale Dec 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants