Support defaults

[vercel]

Support defaults

[Qix-]

@matthewmueller Here's an example for a utility I am writing at the moment:

const args = arg({
	'--help': Boolean,
	'-h': '--help',

	'--out-dir': String,
	'-o': '--out-dir',

	'--numeric-bold': Boolean,
	'-B': '--numeric-bold',

	'--bold': Number,
	'-b': '--bold',

	'--normal': Number,
	'-N': '--normal',

	'--path': String,
	'-p': '--path',

	'--out-name': String,
	'-O': '--out-name'
});

const {
	'--bold': boldWeight = 700,
	'--normal': normalWeight = 400,
	'--out-name': outputName = 'fonts'
} = args;

[rauschma]

@Qix- Suggestion: add this example to the project’s readme.

[rauchg]

Wouldn't destructuring defaults be a better option here? They don't work for null, but if we set undefined that could work

[rauchg]

If so, we should consider doing a major bump to get rid of - and -- in the spec perhaps

[matthewmueller]

Wouldn't destructuring defaults be a better option here?

How would this look?

If so, we should consider doing a major bump to get rid of - and -- in the spec perhaps

I quite like its explicitness but I do forget they're needed every time haha.

Another option could be supplying a function. I just noticed the arg.flag(fn). It seems like that could be the solution.

[Qix-]

I'm 👎 on this. I think this is very clearly getting into scope creep territory.

[matthewmueller]

Sounds good. It's easy enough to do outside of this library.

[matthewmueller]

Looks great, thanks for sharing! Destructuring, aliasing, and defaults in one call – JS is getting so crazy 😬