@spree/docs 0.1.277 → 0.1.278

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -714,9 +714,16 @@ const tokens = await sellerClient.auth.login({
714
714
  sellerClient.setToken(tokens.token)
715
715
 
716
716
  // A user who runs several sellers picks which one they are acting as
717
- sellerClient.setSeller('sel_xxx')
717
+ const { sellers } = await sellerClient.me.get()
718
+ sellerClient.setSeller(sellers[0].id)
719
+
720
+ // The signed-in person edits their own account (name, photo, panel language);
721
+ // the seller business itself is `sellerClient.profile.update(...)`
722
+ await sellerClient.me.update({ first_name: 'Ada', selected_locale: 'de' })
718
723
  ```
719
724
 
725
+ > **NOTE:** `sellerClient.me` is an object with `get()` and `update()`. Code written against `@spree/seller-sdk` 1.0.0-beta.1 or beta.2 that calls `sellerClient.me()` directly keeps working, but that form is deprecated and logs a one-time warning — switch to `sellerClient.me.get()`.
726
+
720
727
  Authentication is JWT only. **There is deliberately no secret-key equivalent**: a key that acts as a seller without a seller signing in is exactly what the Seller API's design exists to prevent. Sign-in fails for a store staff member who runs no seller, even though staff share the same user class.
721
728
 
722
729
  The chosen seller travels as `X-Spree-Seller-Id`. The store is derived from the seller server-side and never sent alongside, so no header a client can set widens what it reaches.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@spree/docs",
3
- "version": "0.1.277",
3
+ "version": "0.1.278",
4
4
  "description": "Spree Commerce developer documentation for AI agents and local reference",
5
5
  "type": "module",
6
6
  "license": "CC-BY-4.0",