mirror of
https://github.com/naturalcrit/homebrewery.git
synced 2026-03-23 02:18:12 +00:00
Updated Folders: Collected Clippings (markdown)
@@ -260,7 +260,7 @@ the owner changes.
|
||||
|
||||
|
||||
|
||||
## DO TAGS *AFTER* FOLDERS
|
||||
#### DO TAGS *AFTER* FOLDERS
|
||||
|
||||
Hmm .. we’re gonna have to hold off on brew tags until we also get
|
||||
user folders implemented .. because users *will() use tags as
|
||||
@@ -282,7 +282,7 @@ filter by them
|
||||
|
||||
|
||||
|
||||
## FOLDERS AS SPECIAL CASE OF TAGS?
|
||||
### FOLDERS AS SPECIAL CASE OF TAGS?
|
||||
|
||||
> Those are just two separate tagging mechanisms. You could have a url
|
||||
route strategy which displays them differently, but I'm not sure why
|
||||
@@ -311,7 +311,7 @@ centric objects).
|
||||
|
||||
|
||||
|
||||
## PUBLIC VS PRIVATE TAGS
|
||||
### PUBLIC VS PRIVATE TAGS
|
||||
|
||||
> All public tags are actually "public:{tag}" and the tag search only
|
||||
looks for ones that match 'public:{tag}'. Or maybe the reverse of
|
||||
@@ -328,7 +328,7 @@ This is all orthogonal to whether a brew is published or not. This is
|
||||
about whether a published brew would have all the author tags made
|
||||
visible on that brew.
|
||||
|
||||
|
||||
[RESOLVED: nope]
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user