-
Notifications
You must be signed in to change notification settings - Fork 320
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
Too Generic Image Input Name #571
Comments
I see how this can cause problems for certain form implementations. Does this sound like a solution that works for you, @robinvandernoord? |
Yes that sounds great! I think I can try to create that option and make a PR if you like. Or would you prefer to build it yourself? |
I would appreciate any help you can give :) |
I have created a PR. I looked into adding a cypress test for it but I didn't find any existing tests related to this feature. Is that correct or am I looking in the wrong place? |
Describe the bug
When using
upload-image
, an input with name="image" is created. This is a very generic name, which can conflict when using EasyMDE in a form.It changed the type from a file upload to a list of file uploads, and the inlined image was also not cleared, so my server received two files instead of one for my other 'image' field.
Using a less generic name like 'easymde-image' would solve this issue.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect easymde to not impact the normal behavior of my form by using a namespaced input or clearing/removing the new input after usage.
Screenshots
Version information
Additional context
This may be more of a feature request than a bug, but it broke my project so I'm reporting it as a bug :)
The text was updated successfully, but these errors were encountered: