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

add comment 3eb43ce8ab338850fb6e5005ab5fee8d on issue 08f0d7ee7842c439382816d21ec1dea2

Browse source
This commit is contained in:
sigil-03 2025-07-15 11:09:06 -06:00
parent f77babb1a4
commit 502e843b2f
1 changed files with 26 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

26
08f0d7ee7842c439382816d21ec1dea2/comments/3eb43ce8ab338850fb6e5005ab5fee8d/description Normal file
View file

@ -0,0 +1,26 @@
maybe there's a delineation that's starting to be drawn here between an "issue" and what the database on the backend uses.
for the filesystem DB, i think it might make sense to have a hashmap that stores everything as a key-value pair, where each key is a file, and each value is the contents of that file.
once we go up the stack, i think it makes sense to have things in concrete structs, since that's easier to reason about.
this also frees up the filesystem DB to get used for other things potentially, not just issues.
so you'd have a system where
```
filesystem
^
|
v
db layer: key/value pair
^
|
v
application layer: concrete structs (like `Issue` etc)
^
|
v
presentation layer: (CLI / TUI / etc.)
```