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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@vue-storefront/next@4.0.0
Major Changes
It shares the data about:
This change will require you to refactor your hooks to make use of the introduced state manager.
As this is only a state management, you will still need to use the hooks to fetch the data and put it into the state.
To make use of the new state solution you will need to change the file
sdk/sdk-context.ts.The type
SfContractis a type that represents the contract between the middleware and the state manager.It is delivered out of the box.
Example of usage:
createSdkContextexported from theclientis changed tocreateAlokaiContext.Also, it no longer returns an array with two elements, but an object with multiple properties.
This change is related to the fact that now it not only provide SDK context but also global state management context and hooks for handling it.
Patch Changes
@vue-storefront/nuxt@5.0.0
Major Changes
It shares the data about:
This change will require you to refactor your composables to make use of the introduced state manager.
As this is only a state management, you will still need to use the composables to fetch the data and put it into the state.
Every part of global state can now be used as refs so reading and writing to them is more straightforward.
Example of usage:
vsftoalokai. Also, the support for thevsfkey in Runtime Envs has been changed toalokai.meta: { name: "@vue-storefront/nuxt", - configKey: "vsf", + configKey: "alokai", compatibility: { nuxt: "^3.0.0", },Patch Changes
@vue-storefront/sdk@3.2.0
Minor Changes
loggeroption to themiddlewareModuleconfig. This option allows you to turn on/off the logging of the SDK requests and responses or to provide a custom logger function.import { initSDK, buildModule, middlewareModule } from "@vue-storefront/sdk"; import { Endpoints } from "@vsf-enterprise/sapcc-api"; const sdk = initSDK({ commerce: buildModule(middlewareModule<Endpoints>, { apiUrl: "http://localhost:8181/commerce", + logger: true, }), });Logger can be also turned on by setting the
ALOKAI_SDK_DEBUGenvironment variable totrue.