"Titleize" letters
nlevchuk opened this issue · 14 comments
I want to 'Titleize' output letters. Either it should be another additional option, like a :titleize_letters, or do it by default? What do you think?
I think it should be another additional option set to true by default cause it looks nicer. Ling, what do you think?
Shouldn't this be a user land feature because they can do it with a simple
map function? That's essentially what we'd would be implementing right?
On Aug 15, 2013 8:11 AM, "Oleg Grishin" notifications@github.com wrote:
I think it should be another additional option set to true by default
cause it looks nicer. Ling, what do you think?—
Reply to this email directly or view it on GitHubhttps://github.com//issues/11#issuecomment-22663390
.
I guess but why not just add it? Is there any big obstacle or an overwhelming reason why we shouldn't do it?
Just seems to not have features that don't relate to pagination. It's like
bloat cause we are parsing the output. It goes beyond the specified purpose
and there's no salient difference between writing map inside or outside the
gem. Let's follow the Unix do one thing well philosophy.
On 15 Aug 2013 11:35, "Oleg Grishin" notifications@github.com wrote:
I guess but why not just add it? Is there any big obstacle or an
overwhelming reason why we shouldn't do it?—
Reply to this email directly or view it on GitHubhttps://github.com//issues/11#issuecomment-22675733
.
Ok. At the end of the day it's just one method....
On Thu, Aug 15, 2013 at 4:18 AM, Lingliang Zhang
notifications@github.comwrote:
Just seems to not have features that don't relate to pagination. It's like
bloat cause we are parsing the output. It goes beyond the specified
purpose
and there's no salient difference between writing map inside or outside
the
gem. Let's follow the Unix do one thing well philosophy.
On 15 Aug 2013 11:35, "Oleg Grishin" notifications@github.com wrote:I guess but why not just add it? Is there any big obstacle or an
overwhelming reason why we shouldn't do it?—
Reply to this email directly or view it on GitHub<
https://github.com/lingz/alphabetical_paginate/issues/11#issuecomment-22675733>.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/11#issuecomment-22677425
.
There's a million ways to parse results. You could capitalize all, or
reverse sort, or only show the first 5 elements etc. It makes more sense to
parse per use and also the method which doesn't have anything to do with
pagination to the result produced. If you feel strongly about it, feel free
to add it though I feel elegant code should try to be as minimalistic as
possible.
On 15 Aug 2013 12:23, "Oleg Grishin" notifications@github.com wrote:
Ok. At the end of the day it's just one method....
On Thu, Aug 15, 2013 at 4:18 AM, Lingliang Zhang
notifications@github.comwrote:Just seems to not have features that don't relate to pagination. It's
like
bloat cause we are parsing the output. It goes beyond the specified
purpose
and there's no salient difference between writing map inside or outside
the
gem. Let's follow the Unix do one thing well philosophy.
On 15 Aug 2013 11:35, "Oleg Grishin" notifications@github.com wrote:I guess but why not just add it? Is there any big obstacle or an
overwhelming reason why we shouldn't do it?—
Reply to this email directly or view it on GitHub<https://github.com/lingz/alphabetical_paginate/issues/11#issuecomment-22675733>
.
—
Reply to this email directly or view it on GitHub<
https://github.com/lingz/alphabetical_paginate/issues/11#issuecomment-22677425>.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/11#issuecomment-22677585
.
Ling, do you mean parse html document? We can't capitalize letters because we don't get just letters. The ViewHelprer forms html code and returns it on page. What we can do with this code, only parse, but it's bad way.
Oh I see what you mean now. Go ahead, sounds like a good idea.
On 15 Aug 2013 18:34, "Nikita Levchuk" notifications@github.com wrote:
Ling, do you mean parse html document? We can't capitalize letters because
we don't get just letters. The ViewHelprer forms html code and returns it
on page. What we can do with this code, only parse, but it's bad way.—
Reply to this email directly or view it on GitHubhttps://github.com//issues/11#issuecomment-22687555
.
Ok )
—
Nikita Levchuk
On Thu, Aug 15, 2013 at 2:09 PM, Lingliang Zhang notifications@github.com
wrote:
Oh I see what you mean now. Go ahead, sounds like a good idea.
On 15 Aug 2013 18:34, "Nikita Levchuk" notifications@github.com wrote:Ling, do you mean parse html document? We can't capitalize letters because
we don't get just letters. The ViewHelprer forms html code and returns it
on page. What we can do with this code, only parse, but it's bad way.—
Reply to this email directly or view it on GitHubhttps://github.com//issues/11#issuecomment-22687555
.
Reply to this email directly or view it on GitHub:
#11 (comment)
^Sorry, I thought you wanted to paginate the actual records returned by alpha_paginate.
Hey guys. What final solution we should accept by this question? Capitalize all letters out of the box or it should be additional parameter?
Capitalise all sounds good!
On 4 Sep 2013 22:16, "Nikita Levchuk" notifications@github.com wrote:
Hey guys. What final solution we should accept by this question?
Capitalize all letters out of the box or it should be additional parameter?—
Reply to this email directly or view it on GitHubhttps://github.com//issues/11#issuecomment-23811548
.
I agree
I am totally for it
On Wed, Sep 4, 2013 at 10:37 PM, Nikita Levchuk notifications@github.comwrote:
I agree
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/11#issuecomment-23813193
.