smartcontractkit / smartcontractkit/chainlink-starknet
Remove example artifact on Gauntlet
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 60
- Forks
- 31
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 2
Description
I'd prefer we avoid adding static artifacts like this and actually add an example contract, compile it and use it.
I assume the idea is this will at one point get extracted to a template repo?
Originally posted by @krebernisak in https://github.com/smartcontractkit/chainlink-starknet/pull/2#discussion_r876232447
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 locating the Gauntlet example artifact and the example-contract build and usage path; the issue names no files or tests. Done means the static artifact is no longer added and a compiled example contract is used instead, with the resulting workflow verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100