-
-
Notifications
You must be signed in to change notification settings - Fork 149
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
Add possibility to make loading of default providers optional #533
Labels
feature
New features
Comments
s1hofmann
added a commit
that referenced
this issue
Sep 17, 2023
s1hofmann
added a commit
that referenced
this issue
Sep 17, 2023
…ading of default clipboard provider via env var
s1hofmann
added a commit
that referenced
this issue
Sep 17, 2023
…ore being able to load alternatives
s1hofmann
added a commit
that referenced
this issue
Sep 17, 2023
…ther native providers as well. Preparing for further refactorings
s1hofmann
added a commit
that referenced
this issue
Sep 23, 2023
* (#533) Move clipboard provider into dedicated package * (#533) Extend provider registry with checks for providers, disable loading of default clipboard provider via env var * (#533) Add safety checks when accessing providers to avoid errors before being able to load alternatives * (#533) Extend constants and provider registry to disable loading of other native providers as well. Preparing for further refactorings * (#533) Update sonar action
Closed by #534 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Short overview
Add possibility to make loading of default providers optional, which allows for more flexibility.
Detailed feature description
This will be the first step in a bigger effort to make all default providers optional.
Making default providers optional will make it possible to replace defaults with custom providers, targeting remote execution of nut.js scripts.
The text was updated successfully, but these errors were encountered: