allow to replace every processor with a custom one #98
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
hi,
i am also not a big fan of this "plural thing".
the user should decide how table or class names should be named.
because this class allows the creation of all models at once, the parameter "--table-name" is not usable at this point.
another example: if someone doesn´t want specific columns in
$fillable = [....]
I now have full control over thisbecause I can replace the "FieldProcessor" with my own one and create everything the way I like.
i would be happy to see a merge here because I believe this little change gives 100% freedom to every user
that has a problem with the default way, things get created.
thanks,
micha