Closed tunnckoCore closed 2 years ago
export const fooBar = hela()
.command('add:community [...qux]', 'foo bar')
.alias(['ens:add:community'])
.action(async ({ flags, _, ...qux }) => {
console.log('zaz', qux);
});
export const addCommunity = hela()
.command('add:community [...socials]', 'Add community links to a collection')
.alias(['add:community', 'add:commumity', 'add:social', 'add:socials'])
.action(async ({ flags, _, ...socials }) => {
console.log('socials', socials);
});
the addCommunity
is ignored currently. This should work:
# the fooBar command
hela add:community a b c
# zaz a b c
hela ens:add:community a b c
# zaz a b c
# the addCommand
hela add:social x y z
# socials x y z
export const createCollection = hela()
.command('ens:create <collection>', 'Create collection')
.alias(['create', 'craet'])
.action(async () => {
console.log('create!');
});
export const foo = hela()
.command('foo <collection>', 'sdfsdfn')
.alias(['create', 'foobie', 'craet'])
.action(async () => {
console.log('foo!');
});
Prints foo!
, instead of create!
. That's atleast noticeable and logical, the latter commands override the previous.
aliases
in the help, when there are no aliases-f, --force
) without default (or if the default is boolean), it doesn't match it (if you pass-f
, opts.f is true, but not--force
- it isfalse
).command('filter <...patterns>', 'descr')
when youhela filter --help
it showshela filter [options]
instead ofhela filter <...patterns> [options]