-
Notifications
You must be signed in to change notification settings - Fork 572
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
Select type is being sorted by the collection key #430
Comments
@andrerpbts I'm working on this |
@seuros Can we please reopen this? I'm still seeing the ordering issue. When building with |
Try master please. |
Tried master - no dice. Aren't master and 3.0.3 identical in the relevant sections? |
@stereodenis may be 7e83193 caused a regression? |
i am also using 3.0.3 and experiencing the same problem |
@andrerpbts this PR should fix right order #459 |
Hi,
I'm using the best_in_place, to edit values with
select
type. But, I discovered that it isn't ordering like the collection I've set.So, after some tests, I figured out if you pass the hash in this way:
You'll get the result:
It's all happens because the JSON's parse. It's ordering by the key number, if a hash is given, see:
So, I think the right way to build this element, is using Array, like:
What do you think?
The text was updated successfully, but these errors were encountered: