Thanks for your interest. The short version:
Open an issue with steps to reproduce, the OrcaSync version (Settings screen), your OS, and the OrcaSlicer version you're syncing against. Logs from View → Toggle DevTools → Console help if the UI is misbehaving.
Open an issue first if it's a non-trivial change — an architecture tweak, a new provider, or a UX shift — so we can agree on direction before you spend time. Small fixes can go straight to a PR.
- Run
cargo fmt --allandcargo clippy --workspace --all-targets -- -D warningsbefore pushing. - Run
npm --prefix frontend run typecheckfor frontend changes. - One logical change per PR. Avoid drive-by refactors in feature PRs.
- New providers go in
crates/provider-<name>/and implementorcasync_providers::SyncProvider.
By contributing you agree your work is dual-licensed under MIT or Apache-2.0, matching the project.