http://localhost/ticket/1438 <p> Many actions in the Action API require parameters. What params are needed should be listed and checked. Because currently, if you get them wrong you simply get a useless 500 error. </p> <p> Currently they are listed in the docs, extracted from the code manually. </p> <p> So you could GET /action/api/package_list to receive not only the help text, but a list of arguments. </p> <p> And if you send an extra or missing argument then an intelligent error message can be returned. </p> <h1 id="implementation">implementation</h1> <p> How about some sort of decorator on the action function: </p> <pre class="wiki">@logic_params(id, offset, limit) def get_package_list(context, data_dict): ... </pre><p> This would do the param checking, and is there a way to extract these params from the function? Or do a registration of the logic function? </p> <p> I'd certainly like to keep the list of the list of params for the function with the function, for ease of reading the code. </p> <p> Another good thing would be to pass in the params named as themselves, rather than having them contained in the data_dict. </p> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/1438 Trac 0.12.3 icmurray Mon, 28 May 2012 11:37:14 GMT http://localhost/ticket/1438#comment:1 http://localhost/ticket/1438#comment:1 <ul> <li><strong>milestone</strong> changed from <em>ckan-v1.7</em> to <em>ckan-backlog</em> </li> </ul> Ticket icmurray Mon, 28 May 2012 11:37:30 GMT http://localhost/ticket/1438#comment:2 http://localhost/ticket/1438#comment:2 <ul> <li><strong>milestone</strong> changed from <em>ckan-backlog</em> to <em>ckan-future</em> </li> </ul> Ticket