On Wed, 9 Apr 2014, Jeremy Ruston wrote:
This rule works fine for everything _but_ application/json which is
why I've suggested this change:
But doesn't that add up to the rule *not* being followed because of the
inconsistent treatment of tiddlers that contain application/json?
That's what I just said.
If that change is made _and_ TW5 starts PUTting and GETting tiddlers
as application/x-tiddler+json, then you will get the results that
you want whatever value you put in the type field of the tiddler.
Does that mean that TW5 should always put tiddlers as
application/x-tiddler+json,
regardless of the type field on the tiddler? And would still be able to
pass along the tiddler's type field in the usual way in the body?
Yes, if/when that change is made the content type for PUTting a JSON
container of _any_ type of tiddler will be as above, and you can set
the 'type' to whatever you want.
There are, of course, other content types with which you can PUT a
tiddler but JSON is the primary one.
--
Chris Dent http://burningchrome.com/
[...]
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.
