v2.0.0-alpha

[aaylward]

Let's use this issue to create a roadmap for humanize v2.

Some things we may want to do:

• Remove methods that were deprecated in 1.x
• Drop support for node 0.6.x Upgrading Grunt #13 dd4d5ca
• Move to grunt ~0.4.1 Upgrading Grunt #13 dd4d5ca
• intword has been removed from the v2.0.0alpha branch in favor of compactInteger.
• Naming conventions are addressed in V2/camel case #26
• truncatenumber is renamed boundedNumber in 98a5be8
• Consider removing intComma as well. I don't think it adds value over formatNumber.
• Consider removing public/ from git as it's really just compiled output, not source code.

[aaylward]

We may want to look into some variation of #43 if we want to have an idea of Humanize(value).method(options).

[b-ash]

I think I like the globally-namespaced nature we have now. The real draw to this is how lightweight it is - the less code / hassle, the better.

[zackbloom]

It shouldn't be all that much code to allow what @aaylward is saying, what about something like this:

extend = (a, b) ->
  for key, val of b when b.hasOwnProperty(key)
    a[key] = b
  a

clone = (obj) ->
  extend {}, obj

methods = {
  doSomething: (a, b, c) ->
}

partiallyApply = (fn, vals..., context) ->
  (args...) ->
    fn.call(context, vals..., args...)

Humanize = (vals...) ->
  if vals?.length
    methods = clone(methods)
    for key, method of methods
      methods[key] = partiallyApply(method, vals..., methods)

  methods

extend(Humanize, Humanize())

That way there is no overhead if you don't use the chaining, and we only add a few lines of code.

[hijonathan]

Both are good first passes. I've seen other implementations, like Moment's (inspired by jQuery I think) and underscore's, that I think are cool too. Thoughts on either of those?

[aaylward]

Something else we may want to consider for this release is supporting more loaders. I think Q has a cool approach: https://github.com/kriskowal/q/blob/master/q.js#L29-L63

[Pasvaz]

It would be really great to support localization and translations using external files for costans allowing the community to add their own translations.

[hijonathan]

@Pasvaz +1 million. I'd love to do that, but I don't have much experience with internationalization. Any ideas to help us get started?

[Pasvaz]

The simplest approach is to keep the language specific strings into separate files indexed by key-value and include/load them according to the language settings, the tricky part is to handle pluralization correctly.

For instance, prefix = 'Less than' would be prefix = t('less-than') and locale.en.js contains less-than = 'Less than' while locale.it.js would contain less-than = 'Meno di'. This is just an example, there are many ways to accomplish this task, you can also load translations into arrays and use them like prefix = lang['less-than'] or even using globals (better to avoid this).

For what regards the localization (dates, numbers, formats) there are plenty of projects that have already localized them, for instance Moment.js support the date format and the day names for many languages, also, the ICU project should support any language afaik. But except pluralization that requires some logic, all those steps are quite trivial.

[seblavoie]

I am currently working on a project on which I would benefit from the localization/translation support feature you previously mentioned. I could sure contribute with a pull request if you guys are interested. I just wanted to make sure the project was still under development first, as this discussion is about a year old.

[b-ash]

@seblavoie I'm happy to take a look at a PR. I18n work can be a bit tricky in this context, especially when dealing with functions like pluralize, pace, etc. We'll need to have some tokens that can be swapped out when translating strings that have context, and I'd recommend moment.js for time-related operations. Do you have any ideas on how you'd approach it here?

[seblavoie]

If fact I did not really have a well defined plan on how I would do it yet. That being said, I also think that going with moment.js would do a great job regarding time operations.

About the l18n, I think the pluralize method wouldn't need much change as we can already specify the alternative plural version (unless I’m missing something?). Although times, ordinal and particularly pace will need to be adapted. I will try to come up with something a little more thought of so we discuss it.

[yairEO]

is this an abandonware? Would like to know taking the time to submit bugs and address owners about thoughts and stuff. it very much seems like one.

[blakeyc]

@aaylward - Is anyone maintaining this project anymore?

I use this frequently for most projects would be happy to start contributing to v2.

[aaylward]

@blakeyc @yairEO the project is maintained, but I should have closed this issue a while ago (it's almost 3 years old now).

I recommend that you submit any changes as PRs into v1.x, and then we can worry about a major version bump in the context of some specific change.