Skip to content
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

keep orphans instead of remove #642

Merged
merged 1 commit into from
Apr 28, 2020
Merged

keep orphans instead of remove #642

merged 1 commit into from
Apr 28, 2020

Conversation

nicoduj
Copy link
Contributor

@nicoduj nicoduj commented Apr 28, 2020

just a proposition if it can help, first time so I hope I saw everything !

@oznu
Copy link
Member

oznu commented Apr 28, 2020

Nice work @nicoduj - thanks for this 😄

@oznu oznu merged commit 9bd31fd into homebridge:master Apr 28, 2020
@oznu
Copy link
Member

oznu commented Apr 28, 2020

I made a small change to only apply the -K flag if the user is running Homebridge >= 1.0.2. This is being published to @test.

@nicoduj
Copy link
Contributor Author

nicoduj commented Apr 28, 2020

Indeed , better this way, even if I hope everyone will upgrade quickly (since from a plugin side maintaining compatibility could be challenge if we want to adopt new prototypes ) . Is there no way to block the upgrade of plugins like config ui on 0.4 branch of homebridge ? By using package.json versioning or some other trick ? It would involve maintaining a legacy branch , but would make code much cleaner if we have to handle such « ifs » no ?

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