comment add-command-for-regenerating-the-cache

1 files changed, 27 insertions, 0 deletions

diff --git a/app/Main.hs b/app/Main.hs
index c3a50fc..59afb73 100644
--- a/app/Main.hs
+++ b/app/Main.hs
@@ -81,6 +81,13 @@
 -- before (or for a short comment at the end) the relecant line(s), so
 -- maybe an `--after/-A` option would suffice.  Not sure what's best
 -- here to be honest. =)
+--
+-- COMMENT I don't mind the `--before|-B` option. I was just wondering out
+-- loud, also related to whether we want to extract some closed part of the
+-- AST, seeing that we already have tree sitter, instead of showing context.
+--
+-- But I don't have a good proposal for that myself. It is not my intention to
+-- block on this issue.
 
 -- TODO Expose all command line options as environment variables
 --
@@ -103,6 +110,10 @@
 -- options/flags, where a env variable does not make sense.  But then,
 -- this would be an optional feature in the library, as well, i guess?
 -- :D
+--
+-- COMMENT I could imagine it not too difficult adding a `fromEnv` modifier
+-- into `O.Parser`. In any case, this does not have to block on that, as,
+-- should we decide to do that, we can always migrate to it later.
 
 -- TODO Add a subcommand which appends the generated ids to the issue in the sourcecode
 --
@@ -135,6 +146,14 @@
 -- would I have to come up with an id.  And if we would decide for
 -- randomized (but easily typeable) generated ids, this would be useful,
 -- I believe.
+--
+-- COMMENT Assuming the we append **the title** as the ID, I don't see much
+-- point of this. Maybe better editor integration that auto-completes `@<<ID>>`
+-- would be more appropriate?
+--
+-- I am sympathetic to random identifiers, cf.
+-- @should-automatically-generated-ids-be-random, as long as they are an
+-- additional mechanisam (so that we can ditch them, should they not work out).
 
 -- FIXME Exclude tags in code blocks
 --
@@ -180,6 +199,7 @@
 -- issues.
 --
 -- @topic ids
+-- @scheduled 2023-10-30
 --
 -- 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
@@ -192,6 +212,8 @@
 -- COMMENT I think I like the idea of adding an id, once we see a change in the
 -- title.  I'm not sure though, when in the workflow this would happen.
 -- I think the id generation topic needs some syncronous discussion. :D
+--
+-- COMMENT ACK
 
 -- TODO Dependencies between issues
 --
@@ -254,6 +276,11 @@
 -- ```
 --
 -- We could still additionally color code them.
+--
+-- COMMENT I propose adding the issue marker as an internal @marker tag. There
+-- can be several such tags if several markers are specified (and we want to
+-- allow that). The first marker should have priority in case we have to pick
+-- one.
 
 -- TODO Add option to group issue list
 --