Implement keyword-based positioning of ellipsis / truncation point

[StephenKoller]

In response to #10.

Feature

Allows user to specify placement of truncation marker (default ellipsis) using a relative keyword 'left', 'center', or 'right'.

Examples

smartTruncate('A quick brown fox jumped over the lazy dog', 18, {position: 'right'});
// returns 'A quick brown fox…'

smartTruncate('A quick brown fox jumped over the lazy dog', 25, {position: 'left'});
// returns '…jumped over the lazy dog'

smartTruncate('A quick brown fox jumped over the lazy dog', 26, {position: 'center'});
// returns 'A quick brown…the lazy dog'

Notes

I used a TDD approach, but the implementation is still rather naïve. I'm interested to see if the control flow could be cleaned up while maintaining legibility.

[coveralls]

Coverage remained the same at 100.0% when pulling 7c41fb2 on StephenKoller:master into 4ac0c7f on millerized:master.

[StephenKoller]

Perhaps this could use a more descriptive name than _start2?

[millerized]

This still looks really great, @StephenKoller! I have decided to move this project over to TSdx for a much improved DX.

I also need to update the dependencies because there are some transitive deps that are flagged as potential security risks. This will most likely require a major version bump on this package. Knowing all this I think it's the perfect time to finally implement your solution for keyword-based positioning!

I am targeting this week to do some of these chores and then we'll look at getting this implemented into the new TS source asap – it should be quick and easy!

Thanks for your patience, friend!

[StephenKoller]

Sounds good to me, @millerized! Have been using TS a lot more lately, looking forward to seeing the next iteration of this micro-lib!