Project
Contributing to Croner
Croner is developed in one repository per language, plus one for this site. Contributions are welcome in all of them.
| Repository | Contents | How to contribute |
|---|---|---|
| croner | JavaScript / TypeScript | CONTRIBUTING.md |
| croner-rust | Rust | Development |
| croner-py | Python | Development |
| croner-dotnet | .NET | Development |
| croner-cpp | C++ | Tests |
| croner-site | This site | See below |
If you're looking to support Croner financially, consider checking out our Sponsorship page.
Issues#
If you spot a problem, search the issues of the repository for that language first. Problems with the pattern syntax or DST handling often affect every implementation, so mention if you have checked the others.
A change to how patterns are read should be made in every implementation, so that a pattern gives the same runs in all languages. Open an issue in croner to discuss it first.
Changing this site#
The site is built from Markdown by a small Deno script, and published to GitHub Pages from the main branch of croner-site.
All pages are in src/ in croner-site, and the site is built from that repository alone.
- The overview, installation, pattern, contributing and sponsorship pages are shared by all implementations.
- The usage, comparison and migration pages are for JavaScript.
- The site follows the implementation repositories:
deno task upstreamlists what has changed in them since the site was last synced.
To build the site locally, install Deno, then run deno task serve in croner-site.