Update for Asana 1.1 and allow add use of body for new tasks

[mmynsted]

The idea is to be able to read the values that changed, such as id to gid. Also I wanted the ability to easily provide any necessary detail for a new Asana task as defined here. To do this easily the body of the POST is populated.

One can merge a template of task details with other detail to form the data object of the POST body.

Example:

I have a template for inserting the new task into two Asana projects. It is stored in my configConsts.lua.

 asanaTaskParameters = {
       projects = {
          [1] = "1200536698010895",
          [2] = "1200674652387402"
       }
    }

Two things are necessary to make this work. The first is being able to join tables. I could not get the built-in or hs.fnutils table tools to work for me. I added a couple of functions that work. I have not tried to improve them. The second thing is simply designating the content type so the Asana service can decode the body of the POST.

reqHeader = tableMerge(reqHeader, {['Content-Type'] = "application/json; charset=UTF8"})

I did not do much with documentation. . .

Here is an example of how I registered this Asana spoon with Seal. (Almost the same as before.)

                        ,["New Asana task in " .. consts.asanaWorkWorkspaceName] = {
                            fn = function(y) spoon.Asana:createTask(y, consts.asanaWorkWorkspaceName, consts.asanaTaskParameters) end,
                              keyword = "astogo"
                           }

I am not sure if it is documented but I am storing the API key in the macOS keychain and retrieve it in the config like this.

 asanaApiKey = hs.execute("security find-generic-password -w -a ${USER} -s asana-api-key | tr -d '\n'")

[cmsj]

pinging @malob as author of this Spoon

[mmynsted]

Is there something else I need to do for this?
I am actively using the code from this MR, and it works well for me.

[cmsj]

Is there something else I need to do for this?

At this stage no - it's always tricky with the Spoons because one person submits them and then others want to make changes. I at least like to ping the original author to see if they have an opinion on the changes.

[cmsj]

@mmynsted looks like there a couple of small docstrings issues, otherwise this is good to merge