read/writeJSON have a json permissions object as an argument however it is hard coded into the read/write functions themselves.
The read/write functions take an object as a parameter that includes the filename to open, success and failure callbacks etc, it'd be worth passing a permissions attribute along with that.
There's no real compelling reason to do this besides making the code somewhat easier to read.
read/writeJSON have a json permissions object as an argument however it is hard coded into the read/write functions themselves.
The read/write functions take an object as a parameter that includes the filename to open, success and failure callbacks etc, it'd be worth passing a permissions attribute along with that.
There's no real compelling reason to do this besides making the code somewhat easier to read.