docs: import zod@latest into docs window
#2254
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for guileless-rolypoly-866f8a ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
extradosages
changed the title
zod@latest into docs windowzod@latest into docs window
|
Anybody know what the review process is here? |
|
🧂 Seems like this pr was implemented by #2432 while we were waiting for review |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This imports
zod@latestinto the browser window on the docs page so that people visiting the page can try it out in the console. It is accessible in the top-level variablez. There's a little console log that pops up, as well.Tests
Tested on Firefox 111.0.1. This mozilla browser compatibility table seems to indicate that this will work everywhere.
Here's a screenshot of the PR in effect on a locally-hosted instance of the page:
