Specify starting number #3
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I really would like to keep ennumit simple, with no configuration (one of the reasons I didn't use another npm package. I don't see why you would need to start at another number other than making this fit some legacy code. If that's the case I'd rather update existing code or not use enumit for that case. Most languages enums are number but you don't specify it. |
added 2 commits
July 2, 2015 07:57
Currently only `options.startNumber` is supported. It specifies that starting number for the first enum (default = 1).
donavon
force-pushed
the
specify-starting-number
branch
from
9a52683
to
b8e5ff0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The last arg passed in
Enumcan be anoptionsobject. Currently onlyoptions.startNumberis supported. It specifies that starting number for the first enum (default = 1).