[Refactor] Split the setup-new command module into focused owners#71
Draft
roomote-roomote[bot] wants to merge 2 commits into
Draft
[Refactor] Split the setup-new command module into focused owners#71roomote-roomote[bot] wants to merge 2 commits into
roomote-roomote[bot] wants to merge 2 commits into
Conversation
Contributor
Author
|
No code issues found. See task |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Split the setup-new onboarding command surface out of a single ~2.6k-line module into focused owners while keeping the public tRPC entry points stable:
Co-located the matching tests with those owners (config, onboarding, queued-tasks).
Why this change was made
Recent setup-onboarding work (Teams handoff, queue claim fencing, and related PRs) kept landing as more branches in one file. That made night-to-night fixes riskier and harder to review. This is a behavior-preserving structure split so each concern has a clear owner going forward.
Impact
No intentional user-facing behavior change. Reviewers and later onboarding work can touch status, config, launch/handoff, or queue lifecycle without carrying the full god module.