sfcc-api
1.0.0-rc.13
Major Changes
- CHANGED
Endpoints
interface. Previously, each endpoint containedcontext
param, which is internal and shouldn't be exposed in the final interface. Now,Endpoints
interface properties don't containcontext
param. If you need to usecontext
param, you should useApiMethods
type.
- import { Endpoints } from '@vsf-enterprise/sfcc-api';
+ import { ApiMethods } from '@vsf-enterprise/sfcc-api';
- REMOVED
ContextualizedEndpoints
type. UseEndpoints
instead.
- import { ContextualizedEndpoints } from '@vsf-enterprise/sfcc-api';
+ import { Endpoints } from '@vsf-enterprise/sfcc-api';
1.0.0-rc.11, 1.0.0-rc.12
Patch Changes
- FIXED
signOut
method randomly failing with 400 error
1.0.0-rc.10
Patch Changes
- CHANGED SFCCIntegrationContext from type to interface to allow declaration merging.
1.0.0-rc.9
Minor Changes
- Adds a SCAPI implenentation for the getOrder method of the orders facade
- Add a method to update an order
Patch Changes
- Updated dependencies
- @vsf-enterprise/sfcc-types@1.0.0-rc.4
1.0.0-rc.8
Patch Changes
- Improve the consistency and readability of the types used in the interface of the callback called after a password reset token is generated
- Updated dependencies
- @vsf-enterprise/sfcc-types@1.0.0-rc.3
1.0.0-rc.7
Minor Changes
- Replace all sensitive values in JWT tokens with generic placeholders before exposing them to the SDK consumer
- Add option to serve encrypted JWTs
1.0.0-rc.6
Patch Changes
- Fixes unsafe access to optional API clients in the auth facade
- Adds basic logging and log level configuration
1.0.0-rc.5
Patch Changes
- Fixes incorrectly constructed refinement parameters in OCAPI product search call
1.0.0-rc.4
Minor Changes
- Changes the middleware config so that the OCAPI settings (ocapiClientId) and the SCAPI settings (scapiClientId, slasClientId, slasClientSecret) are optional. This has the following effects:
- If no settings are provided for OCAPI and/or SCAPI, the respective client will not be used, meaning no auth tokens will be generated and all calls will be directed to the other client, if available.
- If no SLAS secret is provided, we'll assume that the SLAS client in use is public, and the public flows will be used for guest tokens, signing in and password resets.
1.0.0-rc.3
Minor Changes
- Added GetCustomerOrder endpoint for fetching data about selected customer's order
Patch Changes
- Updated dependencies
- @vsf-enterprise/sfcc-types@1.0.0-rc.2
1.0.0-rc.2
Patch Changes
- Fixed the handling token - added getting token values from cookies in the config extension, as well as updating cookies on the set.
1.0.0-rc.1
Minor Changes
- added a sign out SDK method to invalidate authenticated JWTs
Patch Changes
- Updated dependencies: @vsf-enterprise/sfcc-types@1.0.0-rc.1
1.0.0-rc.0
Major Changes
- Stable release of SalesForce integration
Patch Changes
- Updated dependencies: @vsf-enterprise/sfcc-types@1.0.0-rc.0