Open
Conversation
…ify boot requirements
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Simplified provider assignments
This moves binding logic from AppWrapper.vue and App.vue into a single boot file to make it easier to identify required order of providers.
Explanation
Previously, it was awkward to identify the order to declare providers when it comes to tests, and even new features if a provider depends on an existing dependency.
The ordering may still not be perfectly optimized, but it does help to give a general sense of where to start setting up providers.
There doesn't appear to be any real reason that some providers weren't all setup in AppWrapper.vue. It was likely just accumulated over the years. 🤷
I've done a standard run-through and everything seems fine. No errors.