smartcontractkit / smartcontractkit/chainlink-starknet
Jest support required using a cross-fetch workaround which should be removed
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 60
- Forks
- 31
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 2
Description
We got information from the ShardLabs team that this workaround is ready to be removed.
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 reading the linked starknet.js commit (83be37a9e3328a44abd9583b8167c3cb8d882790) to identify the cross-fetch workaround and the Jest-related entry points it changed. Confirm the current Jest setup still depends on it, then remove the workaround and verify the Jest test suite passes without cross-fetch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100