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

[SEMVER-MAJOR] Make juggler a regular dependency #1943

Merged
merged 1 commit into from
Jan 6, 2016

Conversation

bajtos
Copy link
Member

@bajtos bajtos commented Jan 6, 2016

Originally, we (ab)used peer dependencies to ensure there is only one instance
of loopback-datasource-juggler in the dependency tree, so that there is only
one singleton instance of model registry. This was very fragile and might not
have worked in certain edge cases.

We have reworked loopback-datasource-juggler and connectors to not rely on
a single juggler instance anymore. As the last step, juggler became a regular
dependency.

Connect to #275

I tested this change by installing the new loopback version in loopback-example-app and loopback-example-offline-sync to verify it works correctly with both database and remote connector(s).

/to @raymondfeng please review
/cc @ritch

@raymondfeng
Copy link
Member

LGTM

@bajtos
Copy link
Member Author

bajtos commented Jan 6, 2016

@slnode test please

@bajtos
Copy link
Member Author

bajtos commented Jan 6, 2016

Windows tests are failing on the master too, I'll ignore those failures and land this patch.

bajtos added a commit that referenced this pull request Jan 6, 2016
…ar-dependency

[SEMVER-MAJOR] Make juggler a regular dependency
@bajtos bajtos merged commit dd7fb60 into master Jan 6, 2016
@bajtos bajtos deleted the feature/make-juggler-a-regular-dependency branch January 6, 2016 17:44
@bajtos bajtos removed the #review label Jan 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants