UMAprotocol / UMAprotocol/protocol
Add Forge Foundry Support
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 485
- Forks
- 215
- Avg merge
- 18m
- Merged PRs (30d)
- 1
Description
Why
UMA protocol currently lacks native support for the Forge Foundry framework, forcing projects to rely on soldeer for package management. This change is motivated by the need to simplify dependency management for projects using Forge Foundry.
How
- Update the .gitmodules file to include necessary references for Forge Foundry dependencies.
- Add a new lib folder containing the required Forge Foundry libraries.
- Update build scripts and configurations for compatibility with Forge Foundry.
- Introduce a basic foundry.toml configuration file.
- Adjust tests to ensure smooth operation within the Foundry environment.
Resolution
UMA protocol will support integration with Forge Foundry without the need for soldeer, enabling projects to install it as a dependency. Verification will be confirmed through successful builds and passing tests.
Difficulty Score [1-10]
5
Contact
Please contact me or my teammate Rob for further discussion.
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 with the existing .gitmodules, build scripts, configurations, and test setup, then compare them with the requested foundry.toml and new lib folder. Add the Forge Foundry dependency references and compatibility changes, and confirm completion with successful Foundry builds and passing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, solidity
- Domain
- blockchain, build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100