Mathias LANG

Currently, when an error is returned from the server, the client will only do something useful if the `Content-Type` is `application/json`: https://github.com/vibe-d/vibe.d/blob/8b5c7a72aa0dfa4d239efacbc5e6bba7f7e7e272/web/vibe/web/rest.d#L2108-L2116 We should also handle the case where the...

```D /+ dub.json: { "name": "test-rest", "dependencies": { "vibe-d": "~>0.10" } } +/ module server; import vibe.core.core; import vibe.core.log; import vibe.http.client; import vibe.http.router; import vibe.http.server; import vibe.web.rest; import std.stdio; interface...

vibe.core.path: Cross-platform normalization / equality ?

3

I have been trying to adapt dub to the newer path modules, but have hit a lot of issues: 1) The new module isn't always normalized, and there is nothing...

feat: Make GenericPath.normalize return itself

6

This makes writing code much easier as can be seen in the unittest.

Support negation for boolean arguments

2

Some use cases require a boolean argument that is `true` by default. Having a `--no-something` for this is quite handy, as demonstrated by `git`: ``` % git add -h usage:...

`MutuallyExclusive` arguments are not printed in the `--help` following POSIX convention

6

```d /++ dub.json: { "name": "test-mutually-exclusive", "dependencies": { "argparse": "~master" } } +/ import argparse; struct Arguments { @MutuallyExclusive() { @NamedArgument string files; @NamedArgument bool list; } } mixin CLI!Arguments.main!((args)...

`MutuallyExclusive` doesn't work for `PositionalArgument` and `NamedArgument`

5

```d /++ dub.json: { "name": "test-mutually-exclusive", "dependencies": { "argparse": "~master" } } +/ import argparse; struct Arguments { @MutuallyExclusive() { @PositionalArgument(0) string files; @NamedArgument bool list; } } mixin CLI!Arguments.main!((args)...