-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tasks_base.rb#get_tasks() pagination broken #110
Comments
Also allow user config of page size. Fixes Asana#110
I've tweaked the generated code here: https://github.com/Asana/ruby-asana/compare/master...apiology:per_page_for_get_tasks?expand=1 I've tested with my use case and it works great. Happy to offer that as a PR. I tried to regenerate the code from the OpenAPI spec in the hopes I could fix this in the templating process somewhere. Unfortunately, the referenced https://github.com/rossgrambo/swagger-codegen from @rossgrambo is not a valid public repo (see https://github.com/Asana/developer-docs/blob/master/Makefile#L60). The unforked version gives me an error: |
Adds a CLI 'mv' subcommand, which supports adding projects to tasks within the same workspace and changing their sections for now. Move over to get_tasks() in ruby-asana, as get_tasks_for_section() lacks completed_since support. Use forked version of ruby-asana gem for development use, as ruby-asana is pending key bugfixes for checkoff: See * Asana/ruby-asana#109 * Asana/ruby-asana#110
/tasks appears to be a legacy endpoint which requires limit be specified if the number of tasks returned would require pagination:
Unfortunately, 'limit' is not sent in automatically in the Ruby client library, nor is it allowed to be sent in by the client library user. Arguably it should be a keyword argument that defaults to 20 and can be overridden.
As a result, in Ruby, client.tasks.get_tasks() cannot be used when it would return a great number of items.
In addition, the documentation is wrong, as it suggests you can pass in 'limit' as part of the options - this has no effect, as it gets translated to 'opt_limit', which is not recognized by the API.
The text was updated successfully, but these errors were encountered: