Contributing
How the repository is set up, how code is written in it, and how a change reaches a release.
formdef is developed in the open at github.com/maurice-rm/formdef.
A change starts as an issue or a pull request against main. The pages here say what a pull
request needs to be merged.
Setup
The tools, the commands, and the checks a pull request has to pass.
Architecture
The packages, the folders of @formdef/core, and the direction their imports point.
Conventions
How code, tests, documentation and commits are written here.
Performance
What a change may cost the compiler and the renderer, and how both are measured.
Release
Changesets, the version pull request, and what a release publishes.
Scope of a change
A pull request does one thing. An improvement noticed on the way goes into an issue rather than into the same pull request. The public API, the shape of a form config and the words the documentation uses are decided by the maintainer: a change that would alter one of them starts as an issue, before any code.