taproot-manufacturing/entomologist
2
0
Fork 0
Code Issues 1 Pull requests 2 Projects Releases Packages Wiki Activity Actions

add comment bd8d26478108fde4e1a9f32507957e5f on issue 08f0d7ee7842c439382816d21ec1dea2

Browse source
This commit is contained in:
Sebastian Kuzminsky 2025-07-12 15:17:27 -06:00
parent e5fd166bff
commit 7c55fa4dc9
1 changed files with 17 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

17
08f0d7ee7842c439382816d21ec1dea2/comments/bd8d26478108fde4e1a9f32507957e5f/description Normal file
View file

@ -0,0 +1,17 @@
I'm liking the idea of a per-issue key/value store.
I think keys and values are both strings, with possible further
parsing/interpretation for some keys?
For the application in this issue we'd teach ent to create a "finished"
key, maybe when setting the state to Done, with a value of an
ISO8601-style datetime stamp (e.g. "2025-07-12T15:08:58-06:00").
There would be a documented spec of reserved keys and their special
meanings and handling.
Full user access via CLI, maybe something like `ent get VARIABLE` and
`ent set VARIABLE VALUE`? Or `ent variable [NAME[=VALUE]]`?
Or maybe merge this with the tags somehow? Would that be simpler,
or more complicated (for the user)?