asana / asana-api-meta Goto Github PK

I noticed the documentation says there's a way to get all fields for a resource https://github.com/Asana/asana-api-meta/blob/master/src/resources/task.yaml#L17.

However, I can't find on https://asana.com/developers/documentation/getting-started/input-output-options a way to do that. I've tried the wildcard (*), and a few others. Happen to know how to pull all fields for a resource?

┆Issue is synchronized with this Asana task

When fetching tasks of a given project, the memberships somehow looks erroneous :

If, the section a task belongs to has been completed (yes : a competed section), then task['memberships'][x]['section']['name'] is null instead of being the name of the section.

I raised Asana/python-asana#87 issue, but it look like "All we need is Love", sorry I meant Tag ;). Previous tag is more then a year old. And there is 73 commits in master since then.

There was "manual" update of client libraries approximately 10 months ago, Jul'2018 without tagging asana-api-meta, but it is still 10 month ago.

At the moment client libraries are completely missing:

• job
• portfolio
• user_task_list

Isn't that a good time for a fresh 0.12 tag? CC: @rossgrambo.

I am using the Ruby version of the client.

I am assuming that the "sections" resources should be similar to tasks. With that said, ::find_by_project should return a collection. Instead, I get this error:

client.sections.find_by_project(project: PROJECT_ID)
# TypeError: {"id"=>000, "gid"=>"000", "name"=>"THE NAME"} is not a symbol nor a string
# 	/home/vagrant/.rbenv/versions/2.3.6/lib/ruby/gems/2.3.0/gems/asana-0.8.0/lib/asana/resource_includes/resource.rb:20:in `respond_to?'
# 	/home/vagrant/.rbenv/versions/2.3.6/lib/ruby/gems/2.3.0/gems/asana-0.8.0/lib/asana/resource_includes/resource.rb:20:in `block in initialize'
# 	/home/vagrant/.rbenv/versions/2.3.6/lib/ruby/gems/2.3.0/gems/asana-0.8.0/lib/asana/resource_includes/resource.rb:19:in `each'
# 	/home/vagrant/.rbenv/versions/2.3.6/lib/ruby/gems/2.3.0/gems/asana-0.8.0/lib/asana/resource_includes/resource.rb:19:in `initialize'
# 	/home/vagrant/.rbenv/versions/2.3.6/lib/ruby/gems/2.3.0/gems/asana-0.8.0/lib/asana/resources/section.rb:45:in `new'
# 	/home/vagrant/.rbenv/versions/2.3.6/lib/ruby/gems/2.3.0/gems/asana-0.8.0/lib/asana/resources/section.rb:45:in `find_by_project'
# 	/home/vagrant/.rbenv/versions/2.3.6/lib/ruby/gems/2.3.0/gems/asana-0.8.0/lib/asana/client.rb:63:in `public_send'
# 	/home/vagrant/.rbenv/versions/2.3.6/lib/ruby/gems/2.3.0/gems/asana-0.8.0/lib/asana/client.rb:63:in `method_missing'
# 	smorg-console:64:in `<main>'

I guess adding collection: true in line 89 of /src/resources/section.yaml should do the trick. However, I am new at using the api myself, so my guess might be wrong.

Thank you 🙏

It is great that asana api provides a way to save custom data.

Currently the external:data field allows storage of string characters.
It would be great if json objects can be stored so that when I update a task with the following external data

          external: {
            "id": 1234567899,
            "data": "{ 'time_estimate': 3600, 'time_spent': 1482 }"
          }

I can then filter tasks that match for example the custom field time_estimate

client.tasks.findByExternalField({'time_estimate': 3600})
//or
client.tasks.findBy({'external:time_estimate': 3600})

returning a list of tasks

Making sure this sync works

Hi,

We can through the API list tasks by assignee but can we retrieve task by team ?

Regards,

PS : It could be a list of assignee

I had forked this repo a while back to create an Asana R client. At that point, everything was working well. Recently, I updated my fork to make sure I have the latest version of the API. However, if I run npm install followed by gulp build now, I run into the following error.

On googling the error, it seems to be the case that Gulp 3 is not longer supported, and I believe this repo uses Gulp 3. Any pointers on how I can get my build working.

I would like to contribute the Asana R client once I clean this up.

fs.js:34
} = primordials;
    ^

ReferenceError: primordials is not defined
    at fs.js:34:5
    at req_ (/Users/ramnath/Documents/Repositories/ramnathv/asana-api-meta/node_modules/natives/index.js:143:24)
    at Object.req [as require] (/Users/ramnath/Documents/Repositories/ramnathv/asana-api-meta/node_modules/natives/index.js:55:10)
    at Object.<anonymous> (/Users/ramnath/Documents/Repositories/ramnathv/asana-api-meta/node_modules/fs-extra/node_modules/graceful-fs/fs.js:1:37)
    at Module._compile (internal/modules/cjs/loader.js:1139:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1159:10)
    at Module.load (internal/modules/cjs/loader.js:988:32)
    at Function.Module._load (internal/modules/cjs/loader.js:896:14)
    at Module.require (internal/modules/cjs/loader.js:1028:19)
    at require (internal/modules/cjs/helpers.js:72:18)