-
Notifications
You must be signed in to change notification settings - Fork 115
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
Bootstrap.Forms.Field insists on humanising labels that don't need to be humanised #58
Comments
Could you give us an example of handlebars code which does not behaves as expected ? |
Something like this:
-- results in a label of "Name Of An Animal", which aside from looking rather ugly, violates all sorts of grammar rules. |
Yes, this is a bug. If you want to work on a pull request, feel free to do so (=> remove the humanize if the label is provided in the tag, but not if it's determined automatically). |
At the moment, I've just commented out the call to |
Had a few spare moments, did a pull request (separate issue, haven't figured out how to link pull requests to an existing issue yet!). |
OK, used the |
Awesome ! If you open a pull request with this commit, I merge it this morning :) |
…s#58) This allows use cases like custom close buttons or custom submit buttons anywhere in the modal component hierarchy.
Currently if I assign human-readable text to the
label
property of aBootstrap.Forms.Field
-derived control, it insists on dicking around with it via thehuman()
function.And by "dicking around", I mean this:
In my copy of ember-bootstrap, I just commented the call to
human()
out, but it would make sense to add some sort of additional property that would preventhuman()
from being called -- or to make that the default behaviour.The text was updated successfully, but these errors were encountered: