diff options
| author |  Alexander Foremny <aforemny@posteo.de> | 2023-11-10 11:14:45 +0100 |
|---|---|---|
| committer | Alexander Foremny <aforemny@posteo.de> | 2023-11-10 11:14:45 +0100 |
| commit | 8015bdc11b63e46ff4685075e90bb49197076653 (patch) | |
| tree | 1cd51b8d9711c141dff38874744953fed48ae72d /app/Main.hs | |
| parent | 4fd26f9cffd97aeb36435f3220e06b58e4097f17 (diff) | |
@backlog issues, remove @scheduled
Diffstat (limited to 'app/Main.hs')
| -rw-r--r-- | app/Main.hs | 18 |
1 files changed, 16 insertions, 2 deletions
diff --git a/app/Main.hs b/app/Main.hs index e367113..4d3902d 100644 --- a/app/Main.hs +++ b/app/Main.hs @@ -55,11 +55,13 @@ -- -- `--filter '(@assigned aforemny) OR (@due 2023-10-4)'` -- @topic tags +-- @backlog -- TODO Tag improvements (globbing) -- -- I would like to filter `--filter '@assigned *@posteo.de'`. -- @topic tags +-- @backlog -- TODO Add support for ammendments -- @@ -83,6 +85,7 @@ -- ``` -- -- @priority high +-- @backlog -- -- COMMENT Ammendments should generate IssueEvents which can be shown in the issue's log. @@ -95,6 +98,7 @@ -- -- @topic show -- @topic options +-- @backlog -- -- COMMENT Do we expect the code BEFORE an issue to be ever relevant? -- @@ -121,6 +125,7 @@ -- -- @topic options -- @topic settings +-- @backlog -- -- COMMENT Can/ should this be made a feature of optparse-applicative, which we -- could fork? Like, can this work transparently if we fork @@ -158,6 +163,7 @@ -- ``` -- -- @topic ids +-- @backlog -- -- COMMENT Can you elaborate on why this would be useful? I am expecting us to -- do some renaming detection regarding provenance. After that, will it be @@ -199,6 +205,7 @@ -- -- @topic markdown -- @topic tags +-- @backlog -- QUESTION Should automatically generated ids be random? -- @@ -215,7 +222,7 @@ -- issues. -- -- @topic ids --- @scheduled 2023-10-30 +-- @backlog -- -- COMMENT I am not sure we want to automatically append `@id`s to the issue -- description. We probably want to append `@pastId` to an issue if we notice a @@ -253,6 +260,7 @@ -- The items should be ordered with the most blocking issues at the top. -- -- @topic dependencies +-- @backlog -- TODO Relations between issues -- @@ -277,6 +285,7 @@ -- to persist the index in a local cache. -- -- @topic search +-- @backlog -- TODO Display issue type in list and show views -- @@ -285,6 +294,7 @@ -- should be grouped by the type. -- -- @difficulty easy +-- @backlog -- -- COMMENT I imagine emojis might be off-putting to some potential users. I -- would like a configuration option to disable emojis and display the marker @@ -340,7 +350,7 @@ -- -- @topic options -- @topic cache --- @scheduled 2023-10-30 +-- @backlog -- -- COMMENT What is the point of this command? Can't caches be handled -- transparently to the user? @@ -374,6 +384,7 @@ -- -- @topic options -- @topic cache +-- @backlog -- TODO Add format option (Text, JSON, ...) -- @@ -389,6 +400,7 @@ -- -- @topic rendering -- @topic options +-- @backlog -- TODO Add HTTP server -- @@ -403,6 +415,8 @@ -- The JSON-Api offers endpoints `GET /<commit>/` which returns `anissue -- list` as `GET /<commit>/<issue-id>/` which returns `anissue show`. -- All command line arguments are exposed via query parameters. +-- +-- @backlog module Main where |