paritytech / paritytech/polkadot-cli
Check handling of PAPI_BUILTIN_EXTENSIONS
Open
Nobody has claimed this yet.
agent:done
good first issue
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 2
- Avg merge
- 12h 35m
- Merged PRs (30d)
- 4
Description
Seems like some extesnions are papi builtins which are not related to our --ext flag. The --asset is a emxaple for that.
Are there more? Why are some builtin and other don't ? How can we make both work as --ext is more generic .
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 tracing PAPI_BUILTIN_EXTENSIONS and the handling of --asset and --ext in the CLI. Compare which extensions are treated as built-ins, determine why their behavior differs, and define what unified handling should mean; done should include documented behavior and tests for both flags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100