Skip to content

Conversation

@Meldiron
Copy link
Contributor

What does this PR do?

Type definitions in Node were not in sync with actual functionality regarding exceptions.

Test Plan

  • Manual QA

CleanShot 2022-09-19 at 08 06 21@2x

CleanShot 2022-09-19 at 08 06 34@2x

Related PRs and Issues

Have you read the Contributing Guidelines on issues?

Yes 😊

@christyjacob4
Copy link
Contributor

Leaving this open until we address the consistency issue on web vs node

@usamashafiqs
Copy link

When these changes merge ?

@lohanidamodar
Copy link
Member

@christyjacob4 @Meldiron can we push this forward?

@christyjacob4
Copy link
Contributor

@lohanidamodar yes we can 👍 I believe the web sdk has been updated to include this as well

Comment on lines 125 to 130
export class {{spec.title | caseUcfirst}}Exception extends Error {
public code: number;
public type: string;
public response: {{spec.title | caseUcfirst}}ExceptionResponse;

constructor(message: string, code?: number, type?: string, response?: {{spec.title | caseUcfirst}}ExceptionResponse);
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Made web, node and Deno consistent.

Don't we need to do the same for all languages?

@lohanidamodar
Copy link
Member

@Meldiron new version should have solved this right? Is this still relevant?

@lohanidamodar
Copy link
Member

@Meldiron closing this for now, please re-open if required.

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.

6 participants