contributing-to-z-schema

To contribute to z-schema, clone the repository, install dependencies with npm install, create a feature branch, and open a well-scoped pull request after passing lint and tests.

Adding new validators or error codes to z-schema requires understanding the codebase architecture and testing strategies, then implementing the feature alongside appropriate unit and integration tests.

z-schema contributions require running unit and integration tests, alongside linting and formatting checks, to ensure code quality and adherence to the project workflow before submitting a pull request.

Working with z-schema involves TypeScript workflows, so familiarity with TypeScript is needed to fix issues, improve documentation, and navigate the codebase architecture effectively.

Setting up the z-schema repository for local development involves cloning the project, installing dependencies, and running build, lint, and test commands to maintain project hygiene.

Yes, contributing to z-schema involves using submodules for collaboration and quality controls to ensure codebase integrity and streamlined feature implementation.