odd behavior when passing ubik multiple arguments

[joprice]

There are a few situations where ubik behaves oddly when provided multiple parameters. I started by passing a single project folder, which works great, but when trying to pass multiple, only the first is handled. I saw in the example passing an fsproj file, so I passed the two folders as fsproj files, but then it exited immediately with No errors found, not processing either. Then, if I pass a mix of fsproj and fs files, the fsproj file is ignored and the fs file is processed.

I'm sure it's easy enough to check the code and figure out why this is happening, but curious what the recommendation should be for a larger repo with 10 or so projects. If it's not meant to be used any of these ways, I can just write a bash script to wrap it, but perhaps it's an improvement if these different usages work, or a folder, wildcard pattern or sln file could be provided to drive the tool, similar to how fantomas can be passed . to work on all projects in the current directory.

[Zaid-Ajaj]

Hi there @joprice the scenario of passing multiple directories containing the projects is just a matter of a missing feature, happy to accept contributions in this space 😄 maybe passing a solution file can iterate through all the projects instead of using multiple directories

[joprice]

Ok cool. In that case, since dotnet/fsharp projects have explicit names, it's easy to have behavior that is extension based and does what the user is expecting - a folder, a project file, a single file, and a solution file are all identifiable (unless there's some odd conventions I've not yet encountered), so you should be able to mix and match them, and have one function that just handles the list of args and dispatches each appropriately based on extension.

Regarding the solution file, I'm curious how you would parse that. I have been using Ionide.ProjInfo for a utility that builds a mermaid graph for visualizing the dependencies of a solution, and found that it's very slow 10-20s sometimes. I noticed some dotnet cli commands can list project structure much more quickly, but haven't found programmatic access examples, besides ones that shell out and parse the output. I know you've done a lot of tooling projects, so maybe you know a good, snappy goto for that sort of project info metadata.