Closed (fixed)
Project:
Translation Management Tool
Version:
8.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
29 Sep 2015 at 22:56 UTC
Updated:
23 Oct 2015 at 07:04 UTC
Jump to comment: Most recent, Most recent file

Comments
Comment #2
edurenye commentedDone.
Comment #3
edurenye commentedProviding screenshots.

Comment #6
juanse254 commentedwe need tests for this.
Comment #7
edurenye commentedAdded test and rebased.
Comment #10
miro_dietikerI'm a little confused about this.
We are depending on the fact that the last item added is the default? No weights or why is this inverse order from what i expected?
Comment #11
edurenye commentedDone.
Comment #12
juanse254 commentedTests are passing and this was manually tested. Seems to work fine setting to RTBC.
Comment #13
miro_dietikerI was just asking questions about why this sequence change was needed in #7. I didn't ask to change the implementation.
If weights are not needed, we are usually trying to avoid them.
Comment #14
edurenye commentedI tried, and was working, works in both ways.
If the 7 is better, then commit that one if there is nothing wrong with that patch.
Comment #15
miro_dietikerCreated followup #2583329: Fix Operations select list options case on Admin Job overview
Comment #16
berdirI definitely prefer explicit weights.
I've heard that the first time. Using weights in form arrays and operations is a good thing. Among other things, it allows you to prepare for someone wanting to alter your module and you can have space in your form elements (e.g., 5, 10, 15, ..). It's very annoying to try and inject a form element into a form that is not prepared for that.
Committed.