We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
With the upcoming support for plugins (#3), the resulting .plix.yml configuration file might end-up too crowded buy the long plugin names.
.plix.yml
We need to allow plugins to automatically register to plix with an alias so that the user can use just an alias in the .plix.yml file.
Example:
plugins: [python, ruby, c++]
These aliases can never contain a . (otherwise a legacy Python import-style lookup is done instead).
.
To implement this mecanism, we need plugins to be registered somehow when plix starts.
plix
Here is a related interesting read.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
With the upcoming support for plugins (#3), the resulting
.plix.yml
configuration file might end-up too crowded buy the long plugin names.We need to allow plugins to automatically register to plix with an alias so that the user can use just an alias in the
.plix.yml
file.Example:
These aliases can never contain a
.
(otherwise a legacy Python import-style lookup is done instead).To implement this mecanism, we need plugins to be registered somehow when
plix
starts.Here is a related interesting read.
The text was updated successfully, but these errors were encountered: