Skip to content

Conversation

@laurenashpole
Copy link
Contributor

Description

What to review

Testing

Fun gif

laurenashpole and others added 15 commits October 2, 2025 17:18
* refactor: remove unused cors error code

* fix: styling for error messaging

* chore: fix tests

* chore: code review updates

* chore: fix tests
This is easily replaced by actually placing a real instance in the context.
…lue (#648)

* fix(auth): do not clear the entire hash during login, only a token value
* fix(auth): also remove withSid
* fix(deps): update dependency @sanity/client to ^7.12.0

* fix(deps): update pnpm-lock.yaml

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Carolina Gonzalez <carolina@sanity.io>
Co-authored-by: squiggler[bot] <128108030+squiggler[bot]@users.noreply.github.com>
…646)

* fix: auth race condition when using the SDK in the Studio structure
* fix(auth): fix cookie authentication in studio mode
* fix(auth): do not redirect to the login if Studio mode is enabled
Co-authored-by: squiggler[bot] <128108030+squiggler[bot]@users.noreply.github.com>
* chore(deps): update dependency vite to v6.3.6 [security]

* chore: manually update to Vite ^6.3.6

* chore: fix dep compatibility

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Ryan Bonial <4294665+ryanbonial@users.noreply.github.com>
Co-authored-by: Ryan Bonial <ryanbonial@gmail.com>
@vercel
Copy link

vercel bot commented Nov 3, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
sdk-docs Error Error Nov 13, 2025 6:57pm
sdk-kitchensink-react Error Error Nov 13, 2025 6:57pm

@socket-security
Copy link

socket-security bot commented Nov 3, 2025

renovate bot and others added 7 commits November 3, 2025 16:43
…o 8ab049f (#662)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…d7e6 (#661)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Ryan Bonial <4294665+ryanbonial@users.noreply.github.com>
…ion to ef1944e (#660)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* feat: add agent actions
* feat: introduce "source" concept

The following introduces a "source" concept that can be used to query
different types of resources. The long-term vision here is:

- `SanityInstance` should no longer be an inherited tree structure.
  This will rather be a single object which contains global information
  (e.g. token). There will be no re-use of any state across `SanityInstance`.
- All hooks/functions which works on documents will also accept a
  `source` parameter. This is a single parameter (instead of the
  `projectId`/`dataset`) tuple that can easily be passed around.
  If you're making higher-order helpers you just need to accept a
  single source object.
- There are top-level functions which constructs these `source` objects.
  In the future these objects will also contain type information.
  These should also be owned by `@sanity/client`. In this PR we're
  mapping it to the existing experimental resource API, but the
  intention is for `@sanity/client` to provide a proper source-based API
  which we're re-exporting/using here in SDK.
- We'll introduce a new "default source" context as well. This is
  _outside_ of the `SanityInstance` so that you can change it.
- There will be no special support for placing multiple sources in the
  context. The user can always define their own context if they want to
  have access to multiple `source` objects. This gives them more
  flexibility in how to structure their applications.
- If you have fully static data sources you can always hard-code them in
  single file: `export const PRODUCTS = datasetSource(projectId, "datasets")`.

* refactor: enforce explicit client config and add tests to achieve coverage

---------

Co-authored-by: Carolina Gonzalez <carolina@sanity.io>
cngonzalez and others added 2 commits November 7, 2025 11:20
* feat(react): create useSendIntent hook

* refactor: rename to useDispatch intent and enforce intentId / action behavior

* feat: add media library source for intents and kitchensink route

* Update packages/react/src/hooks/dashboard/useDispatchIntent.ts

Co-authored-by: Cole Peters <cole@colepeters.com>

* Update packages/react/src/hooks/dashboard/useDispatchIntent.ts

Co-authored-by: Cole Peters <cole@colepeters.com>

* refactor: rename params option

---------

Co-authored-by: Cole Peters <cole@colepeters.com>
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.

5 participants