@modulify/validator 0.0.2 → 0.2.0

package/.yarnrc.yml

@@ -0,0 +1,5 @@
+enableGlobalCache: false
+
+nodeLinker: node-modules
+
+yarnPath: .yarn/releases/yarn-4.12.0.cjs

package/AGENTS.md

@@ -0,0 +1,82 @@
+# AGENTS.md
+
+## Goals
+- Avoid clarification loops by proposing a concrete interpretation when details are missing.
+- Default to the language of the user's initial message unless they explicitly request a different language.
+- Match the tone and formality of the user's initial message unless they explicitly ask for a change.
+- Treat a language switch in the user's message as an explicit request to respond in that language.
+- If a message is mixed-language, reply in the dominant language unless the user specifies otherwise.
+- Run `yarn lint` before handoff or commit preparation when changed files include code covered by eslint rules.
+- Run `yarn typecheck` before handoff or commit preparation when changed files can affect TypeScript types or module resolution.
+- Run `yarn test` before handoff or commit preparation when changed files can affect runtime behavior.
+- Run `yarn build` before handoff or commit preparation when changed files can affect package exports, bundling, or generated declarations.
+- Do not run the full code check pipeline for markdown-only changes unless the user explicitly asks for it.
+- Do not edit generated artifacts under `dist/` or reports under `coverage/` unless the task explicitly requires it.
+
+## Reporting
+- Keep handoff reports natural and outcome-focused: describe what was done.
+- Do not proactively list skipped optional checks unless the user explicitly asks.
+- Always mention blockers, failed required checks, or other omissions that can affect correctness, safety, or reproducibility.
+
+## Purpose
+This file defines practical instructions for working in the `modulify/validator` repository, with a focus on validation-library development, checks, and local project skills.
+
+## Repository Structure
+- This project is a single-package TypeScript library.
+- Package name: `@modulify/validator`.
+- Main source directories:
+  - `src/` - runtime implementation
+  - `src/runners/` - recursive validation runners
+  - `tests/` - vitest test suite
+  - `types/` - public type declarations and shared typing surface
+- Build output directory: `dist/`.
+- Coverage output directory: `coverage/`.
+
+## Local Environment Prerequisites
+- CI runs on Node `22.x` and `24.x`; prefer Node `22+` locally.
+- Install dependencies with:
+```bash
+yarn install
+```
+
+## Running Checks
+
+### Main Scripts
+- Lint:
+```bash
+yarn lint
+```
+- Type check:
+```bash
+yarn typecheck
+```
+- Test:
+```bash
+yarn test
+```
+- Coverage:
+```bash
+yarn test:coverage
+```
+- Build:
+```bash
+yarn build
+```
+
+### Suggested Validation Order For Code Changes
+```bash
+yarn lint
+yarn typecheck
+yarn test
+yarn build
+```
+
+## Important Project Rules
+- Commit messages follow Conventional Commits.
+- Before creating any commit, always reread `skills/commit-workflow/SKILL.md` and follow it as the source of truth for commit splitting, wording, scopes, and lockfile policy.
+- Getter/helper functions must be free of side effects. Side effects are allowed only by prior agreement and only when there are strong, explicit reasons.
+
+## Local Skills
+- `skills/commit-workflow/SKILL.md` - rules for splitting changes into commits and writing changelog-friendly Conventional Commit messages.
+- `skills/coverage-recovery/SKILL.md` - workflow for analyzing uncovered code paths and improving test coverage without adding artificial tests.
+- `skills/yarn-lock-conflict-resolution/SKILL.md` - safe procedure for resolving `yarn.lock` conflicts during merge or rebase.

package/CHANGELOG.md

@@ -2,6 +2,61 @@
 
 All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
 
+## [0.2.0](https://github.com/modulify/validator/compare/v0.1.0...v0.2.0) (2026-03-09)
+
+
+### ⚠ BREAKING CHANGES
+
+* Validation API was redesigned around typed tuples
+* legacy assertion entrypoints were removed, assertion exports now use camelCase names, and violations now expose structured metadata via violates.{predicate,rule,args}.
+* isObject now returns false on null values, added isShape predicate constructor for checking objects structures
+* Injecting check utility into Assertion
+
+### Features
+
+* Added JSON Schema export entrypoint ([0b3ec5b](https://github.com/modulify/validator/commit/0b3ec5b008418d7e7ceaa4a603341f24dc454b48))
+* Added metadata and introspection API ([16ea412](https://github.com/modulify/validator/commit/16ea41268424dc878271227ad4e58cd2cd089c2d))
+* Added simple runtime predicates for built-in values ([11c9f19](https://github.com/modulify/validator/commit/11c9f1996988e7c3ac45c8632caa1c7198ab2792))
+* Added violation collection utilities ([64e9e36](https://github.com/modulify/validator/commit/64e9e36da63a672263f5ac48ef7b22e992dc6148))
+* **assertions:** Added reusable assertion mixins for strings and numbers ([658dc9f](https://github.com/modulify/validator/commit/658dc9f32d1936fcd080969d55415aa5b450ec05))
+* **combinators:** Added object-level shape refinement runtime ([2e2607f](https://github.com/modulify/validator/commit/2e2607f29211db48e5d46652ccef6b4cc185647d))
+* **combinators:** Added tuple and record validators ([71742f9](https://github.com/modulify/validator/commit/71742f9216c7e20d6c3535af965dc2c134c5b4e8))
+* **combinators:** Added union variant validators ([8b9e131](https://github.com/modulify/validator/commit/8b9e131a06a87e9bf462c492cbf8a6facacb7230))
+* **combinators:** Extended fieldsMatch with nested selectors ([af5801e](https://github.com/modulify/validator/commit/af5801ed21dfa62e3f2ae88ad9e6db130ecbe293))
+* Expanded metadata introspection contracts ([a188152](https://github.com/modulify/validator/commit/a1881526b2bd25d18584b478a1650a23d2a28f16))
+* Injecting check utility into Assertion ([be8b22e](https://github.com/modulify/validator/commit/be8b22e23e968d39ade0198f85944b8f82e3183b))
+* isObject now returns false on null values, added isShape predicate constructor for checking objects structures ([ee70741](https://github.com/modulify/validator/commit/ee70741e6f8ad4f2da0913187b1663b2dc1da6ed))
+* redesign assertion API around structured violations ([acf16f3](https://github.com/modulify/validator/commit/acf16f39e26a38da944805dff8eb20ca416ad174))
+* Shape object API was unified ([c43f6b6](https://github.com/modulify/validator/commit/c43f6b61b3cacf33fca224c9f4ef93c794145028))
+* **types:** Added code-aware violation inference ([f9851db](https://github.com/modulify/validator/commit/f9851db28ac663a59a07fb6ca8396910a20929eb))
+* Validation API was redesigned around typed tuples ([d645441](https://github.com/modulify/validator/commit/d6454412b6ac514ff3c31cce6641fabe11c844c3))
+
+## [0.1.0](https://github.com/modulify/validator/compare/v0.0.2...v0.1.0) (2024-12-22)
+
+
+### ⚠ BREAKING CHANGES
+
+* validator object replaced with validate function, containing sub method sync for synchronous validation
+* Length constraint replaced with HasLength functional assertion
+* Exists constraint replaced with IsDefined functional assertion
+* Each object replaced with Each runner
+* Collection object replaced with HasProperties runner
+* Type "Key" replaced with in-box "PropertyKey"
+* ConstraintCollection type was removed
+* ConstraintValidator was renamed to Validator
+* ConstraintViolation was renamed to Violation
+* d.ts files for exported logic units are now generated and available in dist catalogue
+
+### Features
+
+* Logic redesign and simplification ([b829a1e](https://github.com/modulify/validator/commit/b829a1eb0373cc6069451eb1cdf4767accbe2ee3))
+
+
+### Fixes
+
+* Removed sourcemap ([7e469d0](https://github.com/modulify/validator/commit/7e469d0ca60d854c62a79c54e9b3dba1d3b72657))
+* test coverage ([84912c4](https://github.com/modulify/validator/commit/84912c4a33d58b385a1e0c764c57b3806d658613))
+
 ### [0.0.2](https://github.com/modulify/validator/compare/v0.0.1...v0.0.2) (2024-02-05)
 
 ### 0.0.1 (2024-02-05)

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+docs: CODE_OF_CONDUCT.md.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.