Skip to content
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

Support the meta query parameter in timeEntry #12

Open
kekkis opened this issue Apr 25, 2024 · 0 comments · May be fixed by #13
Open

Support the meta query parameter in timeEntry #12

kekkis opened this issue Apr 25, 2024 · 0 comments · May be fixed by #13

Comments

@kekkis
Copy link

kekkis commented Apr 25, 2024

The meta query parameter, if set to true, will bring with it meta information such as the client name and the project name in the entry.

So an example entry would look like:

  {
    "id": 1555410329,
    "workspace_id": 2949399,
    "project_id": 265931152,
    "task_id": null,
    "billable": false,
    "start": "2022-07-01T23:53:41+00:00",
    "stop": "2022-07-01T23:58:33Z",
    "duration": 292,
    "description": "bug fixes for toggl-track typescript package",
    "tags": null,
    "tag_ids": null,
    "duronly": false,
    "at": "2022-07-05T03:32:23+00:00",
    "server_deleted_at": null,
    "user_id": 4232226,
    "uid": 4232226,
    "wid": 2949399,
    "pid": 265931152,
    "client_name": 'Example client',
    "project_name": 'Example project',
    "project_color": '#2da608',
    "project_active": true
  },

The new values are client_name, project_name, project_color, and project_active.

It seems adding support for this is rather simple in the timeEntry.ts file. The types are simple enough to deduce as well.

@kekkis kekkis changed the title Support the meta query variable in timeEntry Support the meta query parameter in timeEntry Apr 25, 2024
@kekkis kekkis linked a pull request Apr 25, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant