-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[CHORE tests] simplify setupStore registrations #6353
Conversation
cc @HeroicEric This complements #6347 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a good step!
@@ -31,7 +30,6 @@ function initializeStore(registry) { | |||
registerOptionsForType.call(registry, 'adapter', { singleton: false }); | |||
registry.register('serializer:-default', JSONSerializer); | |||
registry.register('serializer:-rest', RESTSerializer); | |||
registry.register('adapter:-rest', RESTAdapter); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Out of curiosity - this isn't a "breaking" change, right? (still acclimating)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct. The existence of this adapter was for tests and private. To use it folks would have had to discover it and looked it up via -rest manually. Given the easy of importing RESTAdapter and no evidence of usage I don’t believe we need to treat this as intimate.
This PR allows for more incremental migration away from
createStore
andsetupStore
to modern test syntax.Specifically it
cc @pete-the-pete @snewcomer