Closed jnsandrew closed 13 years ago
Kind of an interesting feature. I'm curious what the application is, though. Why an external file instead of pulling directly from a url?
Why not have the mobile app read directly from the plugin/url? Say you have placed the json plugin in a template called json/output, and then have your mobile app read from http://yoursite.com/json/output, rather than from a file?
Yeah, if you add terminate="yes" to the plugin, it will output the application/json content type headers, so you shouldn't need a json extension. Also, if you find you do need a json extension, you can always name your template output.json (add the extension to your template name) and the url will mimic a json file http://yoursite.com/json/output.json
Brilliant thanks!
I've added the ability to output data to an external file, within the json:entries function. It was something I specifically wanted for an upcoming project but I think it could be useful for some other people.
In the json:entries tag, it accepts two new parameters:
I've also updated the readme to include these new parameters.