checklist issue for dpack-1 validation conditions
- Dominant language
- TypeScript
- Stars
- 51
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
isValidType and isValidObject
- [ ] typenames are mixedcase alphanumeric plus underscores
- [ ] typenames start with capital letter
isValidObject
- [ ] objectnames are mixedcase alphanumeric plus underscores
- [ ] objectnames start with lowercase letter
isValidPack
- [ ] typenames are equal to the key of the type in `types`
- [ ] objectnames are equal to the key of the object in `objects`
isValidPack
- [ ] typenames and objectnames equal the keys used to name the descriptor objects in the pack
- [ ] Has “network”
- [ ] “network” is a string
- [ ] “network” is not “mainnet” (suggest “ethereum”)
- [ ] Has “format”
- [ ] “format” is a string
- [ ] “format” is “dpack-1”
- [ ] Has “objects”
- [ ] “object” is a (JSON) object
- [ ] Has “types”
- [ ] “types” is a (JSON) object
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by locating the isValidType, isValidObject, and isValidPack entry points, then compare their behavior with each checklist condition. Done means the dpack-1 validation enforces the listed naming, key, network, format, objects, and types requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100