On Tue, Feb 28, 2012 at 10:28 PM, Nolan Darilek <[email protected]>wrote:
> Huh, the "fossil json tags list" output seems inconsistent with these > other two: > There are several options which ... > > In particular, it lists wiki pages and events. I'm not sure how those > qualify as tags, > Interestingly enough: a wiki is just an artifact (like a file) with a special tag wiki-PageName. Each ticket has a tag named tkt-TICKET_UUID. > either via the web or command line interfaces. Not being critical, I'm > just genuinely confused > LOL! You're not the only one. After doing the initial json tags interface i said, "huh?" Note the yellow-marked text in the docs which make note of how confusing/inconsistent the interface is (at least in the context of a JSON API). The impl was based directly on code (mainly queries) from the HTML interface, which is why it uses the formats/options it does. i'd like to change some of it, in any case, and i'm open to concrete suggestions. belt ninja tag" or something. Seriously, tags are confusing when you get > beyond the basics. > Amen. Maybe the JSON API should just support a dumbed-down tags interface? -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
