-
Notifications
You must be signed in to change notification settings - Fork 338
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
Nested form-encoded params don't work #469
Comments
Hi @vereis ! First thanks for opening this issue!
Definitely 👍 In regards to the nested form-encoded params there was some discussion in the past here: #121 But thinking about this again I suppose that it's harmless to accept such params given that today it simply errors out and this way of encoding nested data seems to be widely used. So please if you want send us a PR ❤️ Thanks! |
Oops I did search for existing issues but somehow missed that, sorry for the dupe but glad you're willing to accept a PR ❤️ I'll submit a PR later today thank you! |
Allow nested form params: edgurgel/httpoison#469
Ahoy!
We're using
HTTPoison
to interface with Stripe's Metadata API and tried to do the following:And we noticed that this fails with the following:
I think we can fix this by changing the following
to:
I know the above code is gross, but if you're happy for a contribution I'd be glad to try and clean it up & put together a PR? ❤️
Also, do you have any thoughts about supporting maps as well as keyword lists as param keys? Since you're using
Enum
anyway, you can just say you support both which might make some dialyzer users happy.Thanks again!
The text was updated successfully, but these errors were encountered: