Every property is optional ConnectionForList, even id and name
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- api, backend-api-design
Research direction
Start by comparing the ConnectionForList type with Connection and reviewing change #1093, which introduced the optional properties in v4.22.0. Confirm the intended required fields, especially id and name, and check the API documentation for the list response; the issue is done when the rationale or corrected type requirements are established.
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.
Description
#1093 changed the type from Connection to ConnectionForList but in the process made every property optional, which seems like a rather odd choice considering at least id and name are mandatory.
As asked by @cwkfs, why was this change made?
Reproduction
- Upgrade to v4.22.0
Additional context
No response
node-auth0 version
4.22.0
Node.js version
20
- 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
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
auth0/node-auth0#1204 · 11 comments · 7 reactions ·
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