Skip to content

Conversation

@peterb-l
Copy link
Contributor

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?

  • Bugfix
  • Feature
  • Documentation
  • Code style update
  • Refactor
  • Build-related changes
  • Other, please describe:

Does this PR introduce a breaking change?

  • Yes
  • No

The PR fulfills these requirements:

  • It's submitted to the dev branch (or v[X] branch)
  • When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
  • It's been tested on a Cordova (iOS, Android) app
  • It's been tested on an Electron app
  • Any necessary documentation has been added or updated in the docs or explained in the PR's description.

If adding a new feature, the PR's description includes:

  • A convincing reason for adding this feature (to avoid wasting your time, it's best to start a new feature discussion first and wait for approval before working on it)

Other information:

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).
@peterb-l
Copy link
Contributor Author

$ quasar new store does not automatically add index.js as stated, so the steps added here are required.

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.

1 participant