Shield integrations behind features
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
No files, tests, or entry points are named. Start by surveying where third-party software and hardware integrations enter the Rust project and how configuration is currently handled; done means each integration is shielded behind a feature flag.
Written by the indexing model from the issue text.
Description
All integrations with third-party software/hardware should be shielded behind feature flags.
- Dominant language
- Rust
- Stars
- 50
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
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.
More from ElementsProject/reserves
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
ElementsProject/reserves#6 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
-
Safer Challenge Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
ElementsProject/reserves#4 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in ElementsProject/reserves
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug team:backend track:services-maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cowprotocol/services#4950 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·