summaryrefslogtreecommitdiff
path: root/issues
diff options
context:
space:
mode:
authorjgart2021-10-28 20:31:48 -0400
committerjgart2021-10-28 20:31:48 -0400
commit6751f9eebfba95a8f3fd2373a8eee12254ae9474 (patch)
tree2e08c5cc21549c55b437b26e254e80a02d4a690b /issues
parent1c9077f85e7cc76e0752eb1d0f83a75dd23b1d3f (diff)
downloadgn-gemtext-6751f9eebfba95a8f3fd2373a8eee12254ae9474.tar.gz
Add comment to add-linter issue
Diffstat (limited to 'issues')
-rw-r--r--issues/gnbug/add-linter.gmi8
1 files changed, 8 insertions, 0 deletions
diff --git a/issues/gnbug/add-linter.gmi b/issues/gnbug/add-linter.gmi
index 7992753..1a8a301 100644
--- a/issues/gnbug/add-linter.gmi
+++ b/issues/gnbug/add-linter.gmi
@@ -14,3 +14,11 @@ support.
I am not sure. Pjotr is of the philosophy that we should keep the text as unstructured and unrestrictive as possible, and I agree with this philosophy. Linters are likely to annoy users more than help them. They might discourage casual use of the issue tracker. Especially with tags, we don't really want to restrict the user from coming up with new tags.
WDYT? Am I missing some scenario where the linter could be essential?
+
+Nope, it was just something I thought could be convenient if we wanted to restrict
+the format for tags, etc...
+
+If we'd like to "keep the text as unstructured and unrestrictive as possible" I'm
+fine with that too.
+
+I was just worried about using "invalid" tags. Now, I know it's ok :)