psolymos / clickrup Goto Github PK

Listing use cases for the API:

• building apps by integrating ClickUp API (OAuth flow)
• creating functionality missing from ClickUp GUI (i.e. dependency graphs)
• integrating with workflows (i.e. notification when long running job is done)

These use cases then be added as tutorials/vignettes.

TIL: Environment variables set via Sys.setenv() are shared across all Shiny sessions (as are options). This isn't SUPER surprising (they share a global environment), but it means we can't use clickrup for user-specific things in a Shiny app; everyone using the app would share/update the CU_PAT environment variable.

Would it be feasible to add something like a cu_api_key argument to every function, which defaults to Sys.getenv("CU_PAT")? In Shiny calls, we could set that argument explicitly.

This may be moot if I'm able to regenerate the package from the API definition.

https://dev-doc.clickup.com/333/d/ad-314865/2022-release-notes/ad-675997/release-2-127

The ClickUp API provides a powerful way to manage your existing data and users outside of ClickUp. Since flexibility is our middle name, 🦾 we took it one step further by enabling you to modify Teams, and invite or edit members and guests using existing Custom Roles. 🏙️

Additionally, we've enhanced a number of our API endpoints so you can now Create, Update, Remove, and Retrieve Teams with ease. You can also Retrieve existing Custom Roles within a Workspace, and Assign them while inviting or editing both members and guests. 🤝 Last but not least, we added a Get Workspace Seats endpoint so you can quickly see how many members and guest seats are in use and available within your Workspace.

https://clickup.canny.io/feature-requests/p/get-time-entries-by-task-id-from-api

We recently updated our Time Tracking 2.0 API!
We now include the ability to request task, List, Folder, and Space ids and names, along with task tags when using the Get time entries within a date range and get singular time entry endpoints.

You can also filter results by task, List, Folder, or Space using the new parameters on the Get time entries within a date range endpoint.

Refer to our API documentation for more details!

via cu_get_tasks(archived = NA) .

Add Time Tracking 2.0 API and deprecation warning to Time Tracking Legacy API.

See:

• https://clickup20.docs.apiary.io/#reference/0/time-tracking-legacy
• https://clickup20.docs.apiary.io/#reference/0/time-tracking-2.0

httr2 is a ground-up rewrite of httr that provides a pipeable API with an explicit request object that solves more problems felt by packages that wrap APIs (e.g. built-in rate-limiting, retries, OAuth, secure secrets, and more).

We have a work around for retries, but implementing OAuth flow might be easier with httr2.

ClickUp API v2.0 https://clickup.com/api

clickrup::cu_get_teams()
#> Error in parse_url(url): length(url) == 1 is not TRUE

^{Created on 2021-10-02 by the reprex package (v2.0.1)}

There seem to be a last_page property in the tasks related response objects that can be used to determine if paging is required:

str(Tasks,2)
List of 2
 $ tasks    :List of 1 
  ..$ :List of 34      
 $ last_page: logi TRUE