The 84 markdown files under docs/wiki/ are now published to the project's GitHub Wiki at https://github.com/kingchenc/wickra/wiki — a separate git repository (https://github.com/kingchenc/wickra.wiki.git) that GitHub hosts natively with its own UI, search and history. The flat layout that the GitHub Wiki requires has been generated, all internal cross-links rewritten, and a _Sidebar.md groups the 71 indicators by their canonical 8 families. Effects: - docs/wiki/ is removed from the main repo (-84 files). docs/README.md now just points readers at the Wiki. - PR template + CONTRIBUTING text updated to point at the Wiki instead of the in-repo path. The Wiki repo is separately cloneable and editable via the GitHub web UI. - examples/wasm/README.md cross-link fixed to use the Wiki URL. - The (still in-repo) CHANGELOG keeps its historical references to docs/wiki/ paths — those describe what the tree looked like at past releases and stay accurate as history. - README.md, license, all source unaffected. The Wiki itself ships with _Sidebar.md / _Footer.md generated from the 8-families taxonomy and 503/503 cross-links resolved.
3.4 KiB
Contributing to Wickra
Thanks for your interest in improving Wickra. This document explains how to build the project, the standards a change must meet, and how to get it merged.
License of contributions
Wickra is licensed under the PolyForm Noncommercial License 1.0.0 (see
LICENSE). By submitting a contribution you agree that it is
licensed to the project under those same terms. The Noncommercial license
permits use for any purpose other than a commercial one; keep that in mind
when proposing features or depending on Wickra elsewhere.
Project layout
| Path | Contents |
|---|---|
crates/wickra-core |
The indicator engine — every indicator lives here. |
crates/wickra |
Thin umbrella crate re-exporting wickra-core. |
crates/wickra-data |
CSV reader, tick aggregator, resampler, Binance feed. |
bindings/python |
PyO3 bindings (wickra on PyPI). |
bindings/node |
napi-rs bindings (wickra on npm). |
bindings/wasm |
wasm-bindgen bindings (wickra-wasm on npm). |
examples/ |
Runnable examples. |
docs/ |
Pointer to the project Wiki, which holds all documentation. |
Building and testing
Rust
cargo fmt --all --check
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace
cargo test -p wickra-data --features live-binance
The minimum supported Rust version is 1.75 for the workspace crates and
1.77 for bindings/node; the msrv CI job enforces both.
Python
cd bindings/python
python -m maturin build --release --out dist
python -m pip install --force-reinstall --no-deps dist/wickra-*.whl
python -m pytest -q
Node
cd bindings/node
npm install
npx napi build --platform --release
node --test __tests__/
WASM
wasm-pack build bindings/wasm --target web --release --features panic-hook
wasm-pack test --node bindings/wasm
Standards for a change
- Formatting & lints.
cargo fmtmust leave the tree unchanged andcargo clippy ... -D warningsmust be clean. CI gates both. - Tests. New behaviour needs tests; bug fixes need a regression test.
- Indicator correctness. A new or changed indicator must have a
reference-value test against a known-good source (TA-Lib, pandas-ta, or a
hand-computed value) and a
resettest. - Streaming parity. An indicator's
batchoutput must equal the sequence ofupdatecalls. - Bindings. A change to a public indicator API must be mirrored across the
Python, Node, and WASM bindings, including their type stubs /
.d.ts. - Docs. Update the relevant page on the
project Wiki and the
README.mdwhen behaviour or the public API changes. The Wiki lives in a separate git repository:https://github.com/kingchenc/wickra.wiki.git. - Changelog. Add an entry under
## [Unreleased]inCHANGELOG.md.
Commit and pull-request workflow
- Branch off
main. - Keep commits focused — one logical change per commit, with an imperative subject line and a body explaining why.
- Open a pull request against
mainand fill in the template. - CI must be green before review.
Reporting bugs and proposing features
Use the issue templates under
.github/ISSUE_TEMPLATE. For security-sensitive
reports, follow SECURITY.md instead of opening a public issue.