class level granularity

[grahamdyson]

Currently the C# analyzer represents items and dependencies at the member level. Member ordering in C# is rarely consistent with dependencies within the type e.g. top down or bottom up. If there are is some consistency in member order its usually by implementation i.e. grouping constructors, fields, properties and methods together.

Showing dependency counts between members is likely to distract from the higher level class dependencies when using Eunice for the first time on an existing code bases. Class level granularity will mean dependencies can't be listed as precisely when investigating counts. So even if users aren't interested in member order, the existing member level granularity will still be a useful option.

Having more granular items and dependencies also has a performance penalty when rendering and interacting in Eunice.

[grahamdyson]

released in C# 1.9.0