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

add comment 0efebcbcf60417a54382a408b99dadf5 on issue dd20d3ddc86ee802fe7b15e2c91dc160

Browse source
This commit is contained in:
Sebastian Kuzminsky 2025-07-20 22:59:20 -06:00
parent 6ef9c62d15
commit 7d479da4a6
1 changed files with 21 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

21
dd20d3ddc86ee802fe7b15e2c91dc160/comments/0efebcbcf60417a54382a408b99dadf5/description Normal file
View file

@ -0,0 +1,21 @@
There's a fly in the ointment: we want to store tags as files in a
directory, but file names are not allowed to contain the character `/`,
and some of our current tags use `/` in the tag name.
We could allow subdirectories of the `tags` directory, but it feels
like that breaks the budding database abstraction of "a directory is a
key/value store, filenames are the keys, file contents are the values".
We could forbid `/` in tags and replace them with `.` or `_` or something,
but that's a bit sad because i like `/` as the "hierarchy separator".
Wikipedia claims, and experiment confirms:
> The big solidus ⧸ (Unicode code point U+29F8) is permitted in Unix
> and Windows filenames.
<https://en.wikipedia.org/wiki/Filename#Problematic_characters>
But that feels like madness.
I think the least worst option is to replace `/` with `.` in tags.
Opinions?