-
Notifications
You must be signed in to change notification settings - Fork 576
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
1.15 changes decoding behaviour of []
#1175
Comments
I will try to revert it to the previous behaviour but please note this has always been unspecified, as it has always been ambiguous. :) If you can avoid relying on it, it would be beter. What is your use case? |
Some legacy code that was quickly hacked together and an Ecto schema refactor leading to the changeset wanting other parameters than we use in the form. (The form sends I think you're right that we should not rely on it. I'll probably refactor this when I find some spare time... |
You can also fix it by adding a continuous number:
And then getting |
Unfortunately this is not a straight-forward change :( I have added warnings to the docs and CHANGELOG. |
Just to be clear: this was more of an "is this expected" issue than a real problem. The fix in our code was straightforward, just unexpected because there was nothing in the changelog. So no worries, I'm happy that this is documented as unspecified behaviour. Thank you! |
Hi there,
updating to Plug 1.15, we noticed a breaking change with how parameters from a phoenix form are parsed:
1.14:
1.15:
Just wanted to ask whether this is an expected change or not.
The text was updated successfully, but these errors were encountered: