R2NorthstarTools / R2NorthstarTools/FlightCore
Figure out optimal control flow for launching Northstar
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 94
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
We got a few checks we need to perform before we can launch Northstar.
What is the best order to do them in to reduce number of branches in control flow? First OS then Steam/non-Steam? First Steam/non-Steam, then OS? Other things we need to check?
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.
Research direction
Start by locating the launch checks for Northstar and mapping the existing OS and Steam/non-Steam branches. Compare the possible check orders and identify any additional checks required; done means an agreed control-flow design is documented, with implementation scope clear. No files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, tauri
- Domain
- desktop
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100