Beta Feature Feedback: Report Issues with sanity documents validate

[ricokahler]

Context:
We recently introduced a beta version of a sanity documents validate — a new feature that allows users to download and validate all documents specified in a workspace.

As this feature is still in its beta phase, we're actively seeking feedback from our users to identify and resolve potential issues. This is where you'll report them!

Objective:
This GitHub issue is dedicated to gathering user reports on any problems, bugs, or unexpected behavior encountered while using the document validation command.

How to Report an Issue

To help us effectively address your concerns, please include the following information in your report:

1. Brief Description: A concise summary of the issue.
2. Steps to Reproduce: Detailed steps that led to the issue. Include any specific commands you used.
3. Expected Behavior: What you expected to happen when you executed the steps above.
4. Actual Behavior: What actually happened.
5. Screenshots or Error Messages: If applicable, add screenshots or copy-paste error messages.
6. Environment Details: Information about your operating system, what bundlers you're using if not using the provided one, and any other relevant environment details.
7. Additional Context: Any other information that might be helpful in diagnosing the issue.

Your Contribution

Your feedback is invaluable in helping us improve this feature. We appreciate your time and effort in reporting any issues you encounter. Thank you for your support and for being a part of our community!

[thobas-dnvgl]

Hi. With the new studio facelift, we can't have custom logo components anymore. We use to have a custom one to show which dataset we are currently in. To keep the same functionnality in the facelift, I extract the dataset from the environment variables and I add it in the title like this:

But I get an error, I suspect because the config is not loaded through vite with this command?

[jessetan]

When running sanity documents validate we get the error:

⠹ Loading workspace…
Error: Transform failed with 1 error:
[some path here]/utils.js:46:2: ERROR: The JSX syntax extension is not currently enabled

The interwebs implies this may be solved by enabling an extension in vite.config.ts, however we are not using Vite directly.
Code is a mix of JS and TS.
Sanity 3.25.0
Next.js 13.5.5

[good-idea]

We'd like to use sanity documents validate in CI to ensure that schema changes in development don't make documents in the production dataset invalid. This almost works, but one issue is that it validates draft documents, which are OK to be invalid. Is it possible to use sanity documents validate to only validate published documents?