Detect and offer to open .slnf solution filter files#20
Merged
Conversation
Fido now recognises Visual Studio solution filter (.slnf) files alongside .sln/.slnx wherever it looks for solutions: the branch-only "which solution?" chooser, solution mode, and discovery-by-name. Editors such as Rider and Visual Studio open .slnf directly, so a filtered subset of a solution is now a first-class open target. Full solutions stay preferred: .slnf is listed after .sln/.slnx in the extension preference order, so when a filter sits beside a same-named full solution the .sln/.slnx still wins repository de-duplication and remains the primary target — the filter is offered as an additional choice, not a replacement. FindSolutionsInFolder now derives its globs from the shared extension list so the two can't drift. Adds OpenerService tests covering filter discovery in a folder, discovery of a filter-only repo by name, and the full-solution-wins preference, plus a TestRepoWorld helper for writing solution-style files. Updates CHANGELOG and Features docs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ro23XuZJc8Gep8rNJcGxpN
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
2 participants
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
Fido now recognises Visual Studio solution filter (
.slnf) files everywhere it already looks for.sln/.slnx:Editors such as Rider and Visual Studio open
.slnfdirectly, so a filtered subset of a solution is now a first-class open target.Preference: full solutions still win
.slnfis appended after.sln/.slnxin the recognised-extension preference order. So when a filter sits beside a same-named full solution, the.sln/.slnxstill wins repository de-duplication and stays the repo's primary target — the filter is offered as an additional choice, never a replacement.FindSolutionsInFoldernow derives its glob patterns from the sharedSolutionExtensionslist rather than hardcoding*.sln/*.slnx, so the folder-scan globs and the discovery extensions can't drift apart.Changes
src/Services/OpenerService.cs— add.slnftoSolutionExtensions; deriveFindSolutionsInFolderglobs from that list.tests/Fido.Tests/Services/OpenerServiceTests.cs— three new tests:.sln/.slnx/.slnfare all offered,tests/Fido.Tests/Infrastructure/TestRepoWorld.cs—WriteSolutionFilehelper for writing solution-style files.CHANGELOG.md,Docs/Features.md— document.slnfsupport.Testing
Full suite green locally: 119 passed, 0 failed (
dotnet run --project tests/Fido.Tests). Main project builds with 0 warnings / 0 errors.🤖 Generated with Claude Code
https://claude.ai/code/session_01Ro23XuZJc8Gep8rNJcGxpN
Generated by Claude Code