Support discovering projects through an existing Traversal project

[jrusbatch]

dotnet-affected currently supports discovering projects from an existing solution file via --solution-path, or by recursively searching the repository path (either the current working directory or the path specified via --repository-path).

In order to use dotnet-affected in a repository that already uses the Traversal SDK, users first need to generate a solution file from their existing traversal file, and then provide that solution file to dotnet-affected so it can in turn generate a new Traversal file.

It would be awesome if dotnet-affected could cut out the middleperson and parse an existing Traversal project to determine which project files it should consider.

Thanks for all the work you've put into this project, it's a great tool!

[leonardochaia]

Hi @jrusbatch , sorry for the late reply.

We use dotnet-affected for a monorepo where we don't have solution files but use Traversal SDK and SlnGen to generate the solution files.
In our case, we don't generate the solution to run dotnet affected but use the path discovery instead.

Is there a reason why the project discovery from file system is not enough for you?