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 Aug 22, 2023. It is now read-only.
From the context of a running command, there is no populated property indicating which plugin the command belongs to. We have BaseCommand which has utilities used both by the CLI and plugins. I'd like it to be able to identify the plugin name/config in order to create a separate directory for placing assets so that plugins don't have conflicts when accessing these files.
The text was updated successfully, but these errors were encountered:
From the context of a running command, there is no populated property indicating which plugin the command belongs to. We have
BaseCommand
which has utilities used both by the CLI and plugins. I'd like it to be able to identify the plugin name/config in order to create a separate directory for placing assets so that plugins don't have conflicts when accessing these files.The text was updated successfully, but these errors were encountered: