Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flag's collision in pobtoken deck_spawn command #152

Closed
buhtignew opened this issue Jul 15, 2024 · 1 comment
Closed

Flag's collision in pobtoken deck_spawn command #152

buhtignew opened this issue Jul 15, 2024 · 1 comment
Labels
ambiguity Use this label in case you are receving an ambiguity error

Comments

@buhtignew
Copy link
Collaborator

buhtignew commented Jul 15, 2024

I've tried to run pobtoken deck_spawn my_first_pod_deck -m 1.5 -n 3 -f 490000 -e 500000 command and got the following message:

ERROR: The argument '-n' is ambiguous as it could refer to any of the following arguments: ['name', 'number_of_decimals']

_
The same for the attoken deck_spawn command.

@buhtignew buhtignew added the ambiguity Use this label in case you are receving an ambiguity error label Jul 15, 2024
@d5000
Copy link

d5000 commented Aug 1, 2024

Did 3 changes:

  • solved ambiguity, -n now works for number_of_decimals (positional arguments were renamed)
  • renamed command to attoken/pobtoken spawn, as we don't really need the deck_ prefix and we have the "token" name already in the command
  • supported labeled/named addresses for the tracked address (second positional argument).

Commit: 22b7878

Can be closed if everything works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ambiguity Use this label in case you are receving an ambiguity error
Projects
None yet
Development

No branches or pull requests

2 participants