asset information (previously named meta) schema potential point of failure
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
Research direction
Start by reviewing the API asset schema and the App code that reads information.proof.hash.information. Compare the documented minimum payload with the current validation and handling paths. The work is complete when the finalized schema, strict API validation, and missing-key corner case behavior are agreed and covered.
Written by the indexing model from the issue text.
Description
Concept
The App presumes the information.proof.hash.information in asset exists, but the current API doesn't enforce/guarantee it exists. It's possible to add an asset without information.proof.hash.information key with API. It would be better to handle this corner case.
The current minimum possible information retrieved from API is:
{
"proof":
{
"hash": ""
}
}
Reason/Hypothesis
It's a potential failure point if user upload unexpected data using the API
Suggested Implementation (if any)
The data schema need to be revised to make it reasonable for both the backend API and App. Strict validation and corner case handling should be implemented after the next version of data schema is finalized.
┆Issue is synchronized with this Asana task by Unito
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 7
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 10
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.
More from numbersprotocol/capture-cam
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
numbersprotocol/capture-cam#3359 ·
-
nrem nrem:improvement nrem:space
Difficulty 4/5 3-5 days Newbie friendliness 35/100
numbersprotocol/capture-cam#3392 ·
-
nrem nrem:improvement nrem:space
Difficulty 3/5 1-2 days Newbie friendliness 55/100
numbersprotocol/capture-cam#3391 ·
-
nrem nrem:improvement nrem:space
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
numbersprotocol/capture-cam#3390 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
numbersprotocol/capture-cam#3381 ·
All issues in numbersprotocol/capture-cam
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·