alias support - fixes #30

[StephanHoyer]

No description provided.

[StephanHoyer]

@maranomynet plz review an merge if you are ok with it.

I'll do a release then.

[maranomynet]

Should the order of keys in the translations object matter?

i.e. should this test pass?

it('should be agnostic to the order of key declarations', function () {
  expect(translate.resolveAliases({
    C: '< {{B}} >',
    B: 'foo {{A}} bar',
    A: 'bar',
  })).to.eql(translate.resolveAliases({
    A: 'bar',
    B: 'foo {{A}} bar',
    C: '< {{B}} >',
  }))
})

Supporting this would require a slightly more complicated resolution algorithm, but not that much.

[maranomynet]

It seems that the circular reference detection isn't only detecting circular references.

[maranomynet]

Also, I would have expected this test to pass:

it('should allow multiple aliases per string', function () {
  expect(translate.resolveAliases({
    A: 'bar',
    B: 'foo {{A}} {{A}}',
    C: 'foo {{B}} {{A}}'
  })).to.eql({
    A: 'bar',
    B: 'foo bar bar',
    B: 'foo foo bar bar bar'
  })
})

[maranomynet]

I pushed the failing tests just in case... feel free to revert aaebaad if you think either of these is unreasonable or unnecessary atm.

[StephanHoyer]

Thanks.

Just tried to fix this... not trivial.

[StephanHoyer]

ok, just found a simple solution. Feel free to check again

[maranomynet]

Looks great. I can't think of any other missing features.