Create type guards for the view models
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 36
- Avg merge
- 6d 17h
- Merged PRs (30d)
- 7
Description
Description
Currently neither the ComDOM nor the new implementation of the streaming hook cannot ensure that the object received as a response is of a certain type. To conquer the issue of receiving wrong data and being oblivious about the error, type guard functions might be implemented. @maany please let me know whether this actually should be fool-proofed.
Motivation
No response
Change
No response
Additional Information
- The Rucio API needs to be changed.
Contributor guide
No contributing guide indexed for this repository
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 locating the view models, ComDOM implementation, and streaming hook mentioned in the issue, then inspect how response objects are currently consumed. Determine which response types need guards and confirm the intended scope with maintainers. Done means the relevant responses can be checked for their expected types and incorrect data is no longer accepted silently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100