Complete Pinia setup with index.js and boot#18133
Open
peterb-l wants to merge 1 commit intoquasarframework:devfrom
Open
Complete Pinia setup with index.js and boot#18133peterb-l wants to merge 1 commit intoquasarframework:devfrom
peterb-l wants to merge 1 commit intoquasarframework:devfrom
Conversation
Added detailed steps for setting up Pinia in a Quasar app, including creating index.js and a boot file since the index.js file is not automatically generated (which is a bug).
Contributor
Author
|
$ quasar new store does not automatically add index.js as stated, so the steps added here are required. |
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
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.
Added detailed steps for setting up Pinia in a Quasar app, including creating index.js and a boot file since the index.js file is not automatically generated (which is a bug).
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
The PR fulfills these requirements:
devbranch (orv[X]branch)fix: #xxx[,#xxx], where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information: