Development Workflow
Start the Project
Understand Requirements and Write Code
This is a complex process, but generally involves three things:
- Define the input:
vseed - Define the output:
vseed→advancedVSeed, oradvancedVSeed→spec - Write code to ensure new inputs produce the expected outputs
The playground (apps/website/docs/zh-CN/playground/index.mdx) can be used for debugging and development.
Create New Test Cases
If necessary, consider creating new test cases.
When test coverage decreases, new test cases are required.
In the packages/vseed/tests/* directory, create a new testName.json file and write a VSeed DSL.
Then run:
Run Unit Tests and Update Coverage
Ensure three things:
- All tests pass
- Snapshot changes are as expected
- Coverage has not decreased
Coverage changes will be automatically updated to README.md
Update Options Documentation
If you modify TypeScript definitions for chart types, please update the options documentation.
All type definitions under packages/vseed/src/types/chartType correspond to the options documentation for each chart. If changes are made, please update accordingly.
Publish and Submit
After running pnpm changeset, follow the prompts to:
- Select the packages to change — in most cases, only vseed
- Follow semantic versioning: press Enter twice to skip
majorandminor, then selectpatch - Enter a change description, e.g.:
fix: chart render error caused by only one measure
One feature or bugfix → one changeset → one commit
One Pull Request → one issue
One Pull Request can contain multiple features or bugfixes → multiple changesets → multiple commits