Closed Corniel closed 3 months ago
As with #243, I love where your thinking with these changes but just don't have the bandwidth to bring them in. https://github.com/daveaglick/Buildalyzer/issues/247 is a request for a new maintainer(s) and I think it makes sense to let whoever takes over the project decide the direction of open PRs. Thanks for the work, and hopefully we can find a maintainer soon and get this merged.
@phmonte I think this one is also ready for review. This one should be easy (I think(.
While debugging #244, I noticed that debugging which compiler properties where active was not really clear. So similar to #243, I introduced two dedicated (read-only) types that contain the properties and the items. Potentiality, it can replace the dictionaries in the
AnalyzerResult
. That is, obviously a breaking change.Under the hood,
CompilerProperties
andCompilerItemsCollection
are dictionaries (with case-insensitive keys), but as I think (that can be challenged) having the values without the related key have less value in this case, theTryGet()
method returns aKeyValuePair
like struct that combines the two.Let me know what you think.