diff options
author | Alexander Foremny <aforemny@posteo.de> | 2023-10-17 10:59:24 +0200 |
---|---|---|
committer | Alexander Foremny <aforemny@posteo.de> | 2023-10-17 10:59:26 +0200 |
commit | b24f614f0f6aa8363b12f007a44a5d4bc41ec739 (patch) | |
tree | d509efb7bc312af2596761e3c1c8bf4083725c20 /app/Main.hs | |
parent | da12170e694872fd91f81a27748eed07dc3f75cc (diff) |
make filter type-aware
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.
Diffstat (limited to 'app/Main.hs')
-rw-r--r-- | app/Main.hs | 13 |
1 files changed, 0 insertions, 13 deletions
diff --git a/app/Main.hs b/app/Main.hs index 78b95f2..e8440f7 100644 --- a/app/Main.hs +++ b/app/Main.hs @@ -21,19 +21,6 @@ -- I would like to filter `--filter '@assigned *@posteo.de'`. -- @topic tags --- TODO Tag improvements (priorities) --- --- I would like anissue to support priorities when filtering. Let's for a first implementation say that priorities are represented by an integer-values `@priority` tag on an issue. The `--filter` can be extended for filtering integer-valued tags, and the following syntax: --- --- - `--filter '@priority >1'`, `--filter '@priority <1` --- - `--filter '@priority >=1'`, `--filter '@priority <=1` --- --- At some later point, we can configure `high`, `medium`, `low` to mean --- `1,2,3`, `4,5,6`, `7,8,9` respectively. --- --- Issues having a `@priority` tag whose value is not an integer should be regarded not matching the filter. --- @topic tags - -- TODO Add support for ammendments -- -- The user can ammend more information to an issue which is located at |