-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Fix regression that caused untranslated labels of boolean filters #2206
Fix regression that caused untranslated labels of boolean filters #2206
Conversation
Can you provide a failing test to go along with this? While I didn't check whether 47fe4c5 affected form translations when I wrote it, I don't understand how those changes could have caused this. |
Thank you for the quick reply. I added a new test which fails with 47fe4c5. I think it happens because super is called inside |
Ah... Instead of reverting my commit, how about moving the logic I had put in def input_name
super.to_s =~ search_conditions ? super : "#{super}_eq"
end Does that work? |
Sadly that breaks two tests, because
|
I'll take a closer look at this tomorrow. On May 17, 2013, at 6:55 PM, David Francisco notifications@github.com wrote:
|
i can confirm this bug |
Sorry for the delay. This PR looks good. If you can squash these into a single commit I'll merge this in. If you would, please reference 47fe4c5 from the commit message for traceability. |
Ok, thanks! |
This slightly changes 47fe4c5 in order to do the same thing, while translating labels properly. I'm not sure if it's the best approach, so reject this pull request if you have something different in mind 😉