feat(range): accept one argument

[arpadvas]

Description:

Related issue (if exists):
#4332

[coveralls]

Pull Request Test Coverage Report for Build 7665

• 3 of 3 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.2%) to 96.808%

---

Totals
Change from base Build 7664:	-0.2%
Covered Lines:	5246
Relevant Lines:	5419

---

💛 - Coveralls

[benlesh]

Tentatively, I'm okay with this addition, but:

1. It needs to be discussed with the core team
2. It will have to wait for a minor release. (not a patch).

[benlesh]

NOTE: This is a possible breaking change for JavaScript users doing something like: range(-5) and relying on counting up to "zero" which is undefined. (I haven't tested this, but it seems very corner-casey anyway)

[arpadvas]

NOTE: This is a possible breaking change for JavaScript users doing something like: range(-5) and relying on counting up to "zero" which is undefined. (I haven't tested this, but it seems very corner-casey anyway)

True. range(-5) doesn't work. Shall I update the PR so when range(-5) is applied it'd count up to zero (-4, -3, -2, -1, 0)?

[cartant]

Shall I update the PR

Hmm. But range(-5) counting up to zero would be nothing like lodash - AFAICT - so my vote would be to not have it count up to zero.

[cartant]

LGTM