use `undefined` rather than `null` for data fetching defaults
Open
Nobody has claimed this yet.
upstream
v4
- Dominant language
- TypeScript
- Stars
- 285
- Forks
- 33
- Avg merge
- 22h 38m
- Merged PRs (30d)
- 3
Description
Upstream has been changed.
Please check the changes and port them.
Pull Request
Contributor 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.
Research direction
Start by reviewing the upstream Nuxt pull request linked in the issue and identify the corresponding data-fetching code in Nuxt Bridge. Compare the upstream changes with this repository's implementation. Done means the upstream behavior using undefined rather than null is ported and the relevant checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxt, typescript
- Domain
- web-dev
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100