| Age | Commit message (Collapse) | Author |
|---|
|
Example:
```
anissue list --filter '@title /foo/'
```
|
|
|
|
|
|
|
|
We interpret the following types:
- ISO8601-formatted strings as dates,
- integer-formatted strings as integers,
- all other strings as strings.
If the filter value matches a format, it is cast into the respective
data type. For comparison-based filtering, the tag's value is then cast
into the same data type and comparison is performed type-aware. If the
tag's value is not castable, we consider it not matching.
|
|
The following filter expressions are now additionally valid:
```
--filter @tag <=VALUE
--filter @tag <VALUE
--filter @tag >=VALUE
--filter @tag >VALUE
```
Note that negation needs some re-work. Currently, only `--filter !@tag
<VALUE` is valid, and `--filter @tag !<VALUE` is not. The first version
may not behave as you would expect it.
A tracking issue has been created.
Note that without typing tag values, all comparisons perform
lexicographically on `String`s.
|
|
|
|
|
|
Ditches `ghci` in favor of `cabal repl`.
|
|
|
|
|
Alexander Foremny