FuelLabs/sway
Voir sur GitHubAdd CI job to generate default Forc manifest and compare against a saved version
Open
#1 136 ouverte le 4 avr. 2022
The Sway Bookcigood first issue
Métriques du dépôt
- Stars
- (61 702 stars)
- Métriques de merge PR
- (Merge moyen 22h 6m) (16 PRs mergées en 30 j)
Description
Problems
Currently there are two problems:
- Examples that are built use a local path for the standard library in order to guarantee they don't break. This mean there are no examples that use the default Forc manifest that uses this repo's
masterbranch for the standard library. - Such an example is needed for the docs and potentially in other places. https://github.com/FuelLabs/sway/blob/a40472f2a67aa4907c29af0d079ab360c8892b4b/docs/src/introduction/forc_project.md?plain=1#L25
Tasks
- Manually generate the default
Forc.tomland save it to a directory.examples/might not be a good directory for this since all examples are built as part of CI currently and modifying that job would be more work. - Add a CI job that generates the default
Forc.tomland compares it against the savedForc.toml. If they differ, fail. - Use this saved
Forc.tomlin the book as linked above. - Update
forc initto generate a more elaborate test harness than we have today. Specifically, it should include the most common imports, theabigen, loading and deploying the contract fromout/debug/, the wallet and provider, and the contract instance. - Manually generate the default test harness and save it to a directory.
- Add a CI job that generates the default test harness and compares it against the save one.
- Use this saved test harness in the book.
- Add a CI that runs
forc testwith the default test harness.