⚠ The default branch has just been switched to
main
frommaster
(as of May 15th, 2024). Follow the following instructions to update your local fork.git branch -m master main # rename local branch git fetch origin # fetch from remote git branch -u origin/main main # set upstream git remote set-head origin -a # update remote
When it comes to open source, there are different ways you can contribute, all of which are valuable. Here's few guidelines that should help you as you prepare your contribution.
Before you start working on a contribution, create an issue describing what you want to build. It's possible someone else is already working on something similar, or perhaps there is a reason that feature isn't implemented. The maintainers will point you in the right direction.
The following steps will get you setup to contribute changes to this repo:
-
Fork this repo.
-
Clone your forked repo:
git clone git@github.com:{your_username}/zod.git
-
Run
yarn
to install dependencies. -
Start playing with the code! You can do some simple experimentation in
playground.ts
(seeyarn play
below) or start implementing a feature right away.
For an officially supported isolated dev environment that automatically installs dependencies for you:
F1
in VSCode and start typingDev Containers: Clone Repository in Named Container Volume
to run the command.- For the repo, paste
git@github.com:{your_username}/zod.git
if you're using ssh. - Click
Create a new volume...
and name itzod
and the folder name aszod
.
Note: if you can't see Dev Containers
in the F1
menu, follow this guide to install the needed extension.
In the OSS version of VSCode the extension may be not available.
yarn build
- deletes
lib
and re-compilessrc
tolib
yarn test
- runs all Jest tests and generates coverage badge
yarn test enum
- runs a single test file (e.g.
enum.test.ts
)
yarn play
- executes
playground.ts
, watches for changes. useful for experimentation
Zod uses Jest for testing. After implementing your contribution, write tests for it. Just create a new file under src/__tests__
or add additional tests to the appropriate existing file.
Before submitting your PR, run yarn test
to make sure there are no (unintended) breaking changes.
The Zod documentation lives in the README.md. Be sure to document any API changes you implement.
By contributing your code to the zod GitHub repository, you agree to license your contribution under the MIT license.