You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 22, 2020. It is now read-only.
The plan is already to use yargs-parser to let commands support both positional arguments (the default) and option arguments - like you'd see in a CLI program. This module should depend on an underlying monitor as well.
The command module should have a function for checking permissions of the user running the argument. There will be no "permission" levels, the plan is to extend the base module with a predefined check.
This way you'd just create base classes for each permission type you want. You can handle logic however you please and even create other classes to run to ease the amount of necessary code.
The text was updated successfully, but these errors were encountered:
The plan is already to use yargs-parser to let commands support both positional arguments (the default) and option arguments - like you'd see in a CLI program. This module should depend on an underlying monitor as well.
The command module should have a function for checking permissions of the user running the argument. There will be no "permission" levels, the plan is to extend the base module with a predefined check.
e.g.
This way you'd just create base classes for each permission type you want. You can handle logic however you please and even create other classes to run to ease the amount of necessary code.
The text was updated successfully, but these errors were encountered: