-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
lib: option to allow any file #229
Conversation
Needs this feature 👍 |
+1 |
+1 |
I think this is a valuable addition; there are cases in dynamic systems (e.g. CMS) where the field configuration can't be known before a form is submitted, especially when developing a generic API endpoint that may handle updating different types of objects, as per the GraphQL use case. It seems like the explicit field naming was introduced as a best practice / security feature (?) but for some cases an explicit opt-in to dynamically detect & accept any file fields would be useful. |
@LinusU @jpfluger @hacksparrow any chance we can get an indication of whether this will be merged / implemented? otherwise I'll start working on an alternate solution. |
I could probably merge it for you tonight (Swedish time) 🍰 |
@LinusU, I'm good with this addition. I also appreciate the warning in the readme. |
👍 |
Thanks 💯 |
Released as |
Allows the receiving of files regardless of their fieldname.
I'm still not sure if we should merge this. @jpfluger, @hacksparrow, what are your thoughts?