humanize and human_name don't separate words

+1 I don't feel strongly on how it should be fixed, but I do think it needs an update.

I don't know if this is appropriate because it would make human_name behave differently from human_attribute_name. And I also think that "Post comment" is a better result (more human readable) than "Post Comment".

If we cannot make humanize work properly in such cases ("PostComment" becomes "Post comment"), I would call underscore first and then humanize, which would output the right result.

I'll gladly support any patch that is better than "Postcomment", which is utterly broken.

Post Comment Post comment post comment

Anything other than Postcomment!

So here's a patchfile that uses self.name.underscore.humanize, which as José pointed out, is aligned closer to what human_attribute_name does, and humanize expects underscores things anyway. Win win!

+1 for Justin's patch. Applies nicely and does exactly what I'd expect from human_name.

This doesn't apply cleanly at present, can you rebase it and reupload?

Also the comments don't match the implementation?

Ok, have rebased and corrected the comments (thanks for catching that), new file attached.

+1 for this patch as it's what I expect from this method.

Justin French last patch didn't merged with Rails Edge, updated patch.

(Feel free to change commiter name and email)

Thanks Francesc, thanks Koz!

Can the latest patch be applied to 2.3.X?

Automatic cleanup of spam.

gucci watches