A skeleton that you can use on your PHP project with mysql and nginx.
Should we replace the array of files already existing in the entity object?
In popular PHP framework teams use DI and if they want to use the library then they need to use it as a DI.
Added more readme examples.
Add Dependency injection support
Don't preserve the request field names.
Cleanup and readme update
Moving classes around.
Merge pull request #9 from didslm/fw5-DI-support
Add Dependency injection support
Don't preserve the request field names.
closes #3
Is entity validation required or not for a field part of our library?
#[Image('profile_picture', '/public/pictures', required: true)]
private string $image;
We need to think if we want to deal with entity validation since this is only the upload handling library, usually, projects have their own validation logic which they use. Remove the part:
required: true
So the idea of having a validation inside our library does not sound good.
closes #6
We want to improve file validation by adding more logic to the validations of files.
Remove implementation of required field.
Cleanup Image type attribute
Update Readme
Merge pull request #8 from didslm/fw5-remove-required-field
Remove implementation of required field.
We want to improve file validation by adding more logic to the validations of files.
closes #5
Cleanup Image type attribute
closes #5
Sloved by https://github.com/didslm/file-upload-wrapper/pull/7
We want to throw exceptions from the library and not return \RuntimeExceptions, to have better control over errors.