-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] Project Wildcard Exclusion #23
Comments
Yep this is a good idea. We should be able to use the existing parameters and still make it backwards compatible. |
Ok, I'm working on PR right now. |
@madushans PR is ready for your review. |
Hey sorry I'm away for a few days.. will have a look soon. |
Can this feature be merged into the main branch? It's a great feature and at a quick glance the PR seems good to go. |
hey @EdToro74 @jeffdoolittle It seems like the most popular feature is getting the graph, which is really under-developed right now. So I'll focus more on building a more featured frontend, and eventually move this functionality there. |
Looks like the exclusion is disregarded in the curernt PR, since it continues with the directory search regardless, after looking up project files. I'm planning this feature for the front end piece anyway. So I'll do it there later. |
Thanks for the quick reply, I've worked around the issue by just scripting out all the excludes. Looking forward to the integration when you get there! |
It would be nice to generate diagrams that exclude folders/projects with a given wildcard parameter, such as:
**/*.Tests
**/*.Tests.csproj
This would enable a much simpler and cleaner view in repositories where the test projects live next to their implementations, rather than in a separate
tests
folder with a different project root.The text was updated successfully, but these errors were encountered: