Repository navigation
chore: organize CLI components into feature folders - #136
Merged
Merged
Conversation
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
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.
Summary
The CLI's Components folder had 56 source files in one flat list, making related UI code harder to find. This PR groups those files into feature folders, following the organization already used by Services.
What changed
@namespace MandoCode.Componentsto moved Razor components. Their type names stay the same, preserving existing component references, tests, and Desktop compatibility.Why this was done
Developers can now find a feature's components together—for example, prompt and autocomplete components under Input, and workspace tabs and pane layouts under Workspaces. The folder guide also gives future components a clear home.
How it was tested
Notes
This is source organization only; it changes no component logic, UI behavior, dependencies, or version numbers. Existing tests cover the relocated components. The local launch-settings edit is excluded, and this PR does not change Desktop's pinned engine revision.