This is more of a question than an issue at this point, but as CKAN goes through a major revision, the utility and form of this library should be put into question. A well documented JSON API and the Frictionless Data libraries may be preferable to maintaining this module for anything more than backwards compatibility. Could someone from the core team weigh in, please?
@loleg i'm actively working on a "ckan 3" JS SDK and there should be a release out soon. It's more a PoC at this point since ckan v3 does not exist. I also hope it might merge back into here when the time comes.
This is more of a question than an issue at this point, but as CKAN goes through a major revision, the utility and form of this library should be put into question. A well documented JSON API and the Frictionless Data libraries may be preferable to maintaining this module for anything more than backwards compatibility. Could someone from the core team weigh in, please?