Skip to content

Conversation

@mattvagni
Copy link
Member

@mattvagni mattvagni commented Jul 10, 2023

As part of this I've also moved all CI to use node 18 and pnpm.

@vercel
Copy link

vercel bot commented Jul 10, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
typescript-sdk ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 10, 2023 10:36am

### UnknownError

[(view source)](./src/error.ts)
Fallback error type when something unexpected happens.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Realised this was missing from the readme so I documented this as well!

"rollup-plugin-esbuild": "^5.0.0",
"typedoc": "^0.24.7",
"typedoc-plugin-missing-exports": "^2.0.0",
"typescript": "^5.1.6",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Had to install typescript since pnpm is a lot stricter than npm (which is a good thing)

* Resolve an issue for a customer.
*/
async resolveIssue(
input: VariablesOf<typeof ResolveIssueDocument>['input']
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This feels a little 'raw' for an SDK, this could just be issueId and we construct the input

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is what it is but just as a named argument (notice the 'input' at the end):

This means this is valid:

  const foo = await client.resolveIssue({
    issueId: 'it_123'
  })

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or did you mean: resolveIssue('asda') would be nicer?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The latter

@mattvagni mattvagni merged commit 34c06ba into main Jul 10, 2023
@mattvagni mattvagni deleted the issues-queries branch July 10, 2023 10:55
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 this pull request may close these issues.

4 participants