Skip to content

feat(extensibility): setting a custom path for the extensions #4107

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

Merged
merged 1 commit into from
Nov 8, 2018

Conversation

ventsislav-georgiev
Copy link
Contributor

@ventsislav-georgiev ventsislav-georgiev commented Nov 8, 2018

PR Checklist

What is the current behavior?

There is no way to set a different path for loading the CLI extensions.

What is the new behavior?

There is a property pathToExtensions which can be set on the extensibilityService.

@ventsislav-georgiev ventsislav-georgiev self-assigned this Nov 8, 2018
@ventsislav-georgiev ventsislav-georgiev changed the title Allow setting a custom path for the extensions feat(extensibility): allow setting a custom path for the extensions Nov 8, 2018
@ventsislav-georgiev ventsislav-georgiev changed the title feat(extensibility): allow setting a custom path for the extensions feat(extensibility): setting a custom path for the extensions Nov 8, 2018
@ventsislav-georgiev ventsislav-georgiev force-pushed the vgeorgiev/change-extensions-path branch from 1d99bdc to 9459432 Compare November 8, 2018 09:44
@ventsislav-georgiev ventsislav-georgiev force-pushed the vgeorgiev/change-extensions-path branch from 9459432 to c085a5c Compare November 8, 2018 09:45
@ventsislav-georgiev ventsislav-georgiev merged commit 427f482 into master Nov 8, 2018
@ventsislav-georgiev ventsislav-georgiev deleted the vgeorgiev/change-extensions-path branch November 8, 2018 11:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants