| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | chore: Update setup-zig to v2update-zig-setup-to-v2 | 2025-05-07 | 3 | -14/+21 | |
| | | |||||
| * | doc: Don't autogenerate the README | 2025-03-27 | 3 | -164/+0 | |
| | | |||||
| * | Release 0.10.00.10.0 | 2025-03-05 | 1 | -1/+1 | |
| | | |||||
| * | Add minimum_zig_version | 2025-03-05 | 1 | -0/+1 | |
| | | |||||
| * | chore: Update to latest version of zig | 2025-03-03 | 1 | -3/+12 | |
| | | |||||
| * | chore: bump deploy-pages action version | 2025-02-24 | 1 | -1/+1 | |
| | | |||||
| * | Update README.md.template | 2025-02-24 | 1 | -3/+3 | |
| | | |||||
| * | Update README.md | 2025-02-24 | 1 | -3/+3 | |
| | | |||||
| * | chore: Update upload-pages-artifact | 2025-02-21 | 1 | -1/+1 | |
| | | |||||
| * | chore: Update upload-artifact | 2025-02-21 | 1 | -1/+1 | |
| | | |||||
| * | fix: More than 2 positionals not parsing correctly | 2025-02-21 | 1 | -26/+44 | |
| | | | | | Fixes #149 | ||||
| * | chore: update to zig version 0.14.0-dev.2837+f38d7a92c | 2025-01-19 | 1 | -2/+2 | |
| | | |||||
| * | Patch up README and fix comments in example files. (#143) | 2024-11-25 | 6 | -56/+52 | |
| | | | | The readme was also reflowed to 100 cols. I probably should have put that in a separate commit but oh well. The comments were not subjected to reflowing (yet). | ||||
| * | refactor: switch on signedness | 2024-11-15 | 1 | -33/+27 | |
| | | |||||
| * | fix: add uint parsing function | 2024-11-15 | 1 | -17/+54 | |
| | | | | | | | In order to get the more precise `ParseIntError.InvalidCharacter` error instead of `ParseIntError.Overflow` when a negative number is passed to a usize, uX typed argument, I use the `fmt.parseUnsigned` function. | ||||
| * | chore: Update to latest version of zig | 2024-11-04 | 1 | -9/+38 | |
| | | |||||
| * | fix: Subcommand example comments needs a scroll to be read | 2024-10-24 | 2 | -12/+12 | |
| | | |||||
| * | docs: Add subcommand example | 2024-10-24 | 4 | -3/+215 | |
| | | |||||
| * | feat: Support multiple positionals of different types | 2024-10-24 | 5 | -78/+192 | |
| | | |||||
| * | refactor: positonals type now depend on the number of values taken | 2024-10-22 | 1 | -35/+94 | |
| | | | | | | | For `Values.one` positionals will be of type `?T` For `Values.many` positonals will be of type `[]const T` | ||||
| * | refactor: Always access using full namespace | 2024-10-22 | 12 | -281/+232 | |
| | | | | | This is my new preferred style of programming Zig :) | ||||
| * | feat: Add `terminating_positional` to `clap.ParseOptions` | 2024-10-22 | 1 | -3/+49 | |
| | | | | | | | | | This option makes `clap.parse` and `clap.parseEx` stop parsing after encountering a certain positional index. Setting `terminating_positional` to 0 will make them stop parsing after the 0th positional has been added to `positionals` (aka after parsing 1 positional) | ||||
| * | chore: Correct eval branch quota comment in `countParams` | 2024-10-22 | 1 | -2/+2 | |
| | | |||||
| * | refactor: Remove workaround in `parseEx` that required `anyerror` | 2024-10-22 | 1 | -47/+22 | |
| | | |||||
| * | Move updated README to template | 2024-09-21 | 1 | -7/+12 | |
| | | |||||
| * | Make installation section of readme even more clear | 2024-09-16 | 1 | -7/+12 | |
| | | | | | | | | The installation section no longer assumes that all developers use the master branch of Zig. Instead if provides different steps depending on which Zig version developers are using. Related #61 | ||||
| * | fix: Cicd use `with: master` as `latest` is the default | 2024-09-13 | 2 | -2/+6 | |
| | | |||||
| * | chore: Use mlugg/setup-zig instead of goto-bus-stop/setup-zig | 2024-09-13 | 2 | -9/+3 | |
| | | |||||
| * | chore: Run jobs weekly instead of daily | 2024-09-13 | 1 | -1/+1 | |
| | | |||||
| * | adapt to latest zig changes | 2024-08-30 | 2 | -5/+5 | |
| | | |||||
| * | count codepoints instead of bytes, to determine width | 2024-08-30 | 2 | -16/+162 | |
| | | | | | | | | | | | | A complete solution would be to count grapheme clusters, but that would require adding a dependency on something like zg. Counting codepoints will ensure that typical non-ASCII text is supported, but you can still throw it off with more complex Unicode constructions, which might not be so useful in help text. Fixes #75 | ||||
| * | feat: Allow for the assignment separator to be configured | 2024-07-18 | 4 | -116/+188 | |
| | | |||||
| * | Update to newest version of zig | 2024-07-17 | 1 | -1/+1 | |
| | | |||||
| * | Update to latest zig0.9.0 | 2024-06-16 | 1 | -4/+4 | |
| | | | | | | | See https://github.com/ziglang/zig/pull/19847 Compatibility with Zig 0.13.0 remains unchanged | ||||
| * | Add installation instructions to README | 2024-06-09 | 2 | -0/+30 | |
| | | |||||
| * | gitignore: Add new zig-cache folder | 2024-05-31 | 1 | -1/+1 | |
| | | |||||
| * | Update for latest zig | 2024-05-30 | 1 | -1/+1 | |
| | | |||||
| * | Use b.path instead of manually setting the fields | 2024-05-16 | 1 | -3/+3 | |
| | | |||||
| * | Updated `build.zig` to support Zig 0.13.0-dev.211+6a65561e3 | 2024-05-16 | 1 | -3/+3 | |
| | | |||||
| * | Remove zig.mod0.8.0 | 2024-04-21 | 1 | -5/+0 | |
| | | |||||
| * | Arguments: Ensure no member of `fields` is undefined | 2024-03-30 | 1 | -2/+9 | |
| | | | | | related #122 | ||||
| * | Updated to latest zig | 2024-03-12 | 1 | -1/+1 | |
| | | |||||
| * | LICENSE: Remove year | 2024-02-24 | 1 | -1/+1 | |
| | | |||||
| * | cicd: Only depend on major versions | 2024-02-02 | 2 | -3/+3 | |
| | | |||||
| * | Remove gyro.zzz | 2024-02-02 | 1 | -14/+0 | |
| | | | | | Gyro is dead. Rest in peace. | ||||
| * | Update to latest version of zig | 2024-01-09 | 2 | -2/+8 | |
| | | |||||
| * | Update to latest master | 2024-01-05 | 1 | -5/+5 | |
| | | |||||
| * | Add autodoc website | 2024-01-02 | 3 | -0/+61 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds a `zig build docs` step that builds the documentation website and writes it to zig-out/docs. It further includes a GitHub Workflow that publishes this website to GitHub Pages. The GitHub Workflow is divided into two jobs: - build: builds the documentation and uploads it - publish: downloads the documentation and publishes it These are separate jobs to minimize permissions available to the build job. This workflow runs on two events: - after every push to master - `workflow_dispatch`: this allows manually running the workflow from its *Actions* page if something went wrong --- **Important pre-merge steps:** If this PR is accepted, the following steps should be taken before merging the PR: 1. Go to **Settings** for the repository 2. Select **Pages** on the left under *Code and automation* 3. Under *Build and deployment* set **Source** to **GitHub Actions** 4. Merge the PR. If the steps are missed, the PR will merge just fine, but the docs job will fail immediately on merge. This can be remedied by following steps 1-3 above, and either adding a new commit on master, or manually firing the workflow from the Actions > API Reference page. | ||||
| * | Remove the default allocator from `ParseOptions` | 2023-12-13 | 6 | -10/+41 | |
| | | | | | fixes #111 | ||||
| * | Fix short only params not getting fields in `Arguments` | 2023-11-16 | 1 | -10/+11 | |
| | | | | | fixes #84 | ||||