V5 Nullability seems... wrong?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- api
Research direction
Start by reviewing the V5 TypeScript type definitions and the Fern-generated API source mentioned in the issue, then compare response fields with the API documentation. Identify which fields are required or optional, including the invitation ID, organization ID, invitee, and inviter. Done means the generated definitions accurately represent the API's nullability.
Written by the indexing model from the issue text.
Description
Checklist
- I have looked into the Readme, Examples, and FAQ and have not found a suitable solution or answer.
- I have looked into the API documentation and have not found a suitable solution or answer.
- I have searched the issues and have not found a suitable solution or answer.
- I have searched the Auth0 Community forums and have not found a suitable solution or answer.
- I agree to the terms within the Auth0 Code of Conduct.
Describe the problem you'd like to have solved
With V5, it appears that every single field on responses is nullable. Up to and including the ID field on any given element. This can't possibly be correct, and because I know that some of these fields are non-null, I've in some places added asserts or ?? '' because I know they'll be there, but making everything optional means, simultaneously, that I have no idea what is actually optional. Here is one simple example -
export interface CreateOrganizationInvitationResponseContent {
id?: string;
organization_id?: string;
inviter?: Management.OrganizationInvitationInviter;
invitee?: Management.OrganizationInvitationInvitee;
...
}
An invitation will always minimally have an id, an org id, and an invitee - right? I think many of the rest of these are non-null too, but consider these as a starting point. Additionally, the Invitee and Inviter objects both have their properties as non-null, which feels odd?
Describe the ideal solution
Please update the type definitions to accurately reflect nullability. The type files say you're using Fern to generate them from an API - maybe one or both of those need to be updated to address this?
- Dominant language
- TypeScript
- Stars
- 683
- Forks
- 319
- Avg merge
- 1d 30m
- Merged PRs (30d)
- 13
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from auth0/node-auth0
-
createManagementAuth drops the custom fetch option from clientOptionsPossibly taken @RaphaelFakhri claimed this 28 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
auth0/node-auth0#1432 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 70/100
auth0/node-auth0#1434 · 3 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
auth0/node-auth0#1387 · 1 comment · 2 reactions ·
Maintainers usually reply within 1 day
-
bug
Difficulty 5/5 Over a week Newbie friendliness 35/100
auth0/node-auth0#1295 · 2 comments ·
Maintainers usually reply within 1 day
-
bug vNext
Difficulty 3/5 Half a day Newbie friendliness 38/100
auth0/node-auth0#1106 · 3 comments · 1 reaction ·
Maintainers usually reply within 1 day
All issues in auth0/node-auth0
Similar issues
-
`@angular/[email protected]` depends on vulnerable Vite 7.3.7 - GHSA-p4f5-76q4-ffq7 (Critical RCE)Openarea: @angular/build
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
angular/angular-cli#34764 ·
Maintainers usually reply within 1 day
-
status/need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
google-gemini/gemini-cli#30384 · 1 comment ·
Maintainers usually reply within 1 day
-
P2
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
LucasSantana-Dev/Lucky#3150 ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority: low size: XS
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day