You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You already capture telemetry that indicates how many lines of code aren't necessary to be typed as a result of using aspects. I would propose that you add some way (e.g. a modal window in VS at the very least) so that developers can see that information themselves (without counting the current lines, applying a divorce, counting the lines and then reverting the divorce).
I'm just curious about my own statistics (which seem higher than the advertised numbers) and especially since you have a free tier, this would provide excellent material to developers eager to convince their managers of the value of Metalama with a practical value against their own code base.
Thanks for the consideration!
The text was updated successfully, but these errors were encountered:
Hello @WhitWaldo, thank you for submitting this issue. We will try to get back to you as soon as possible.
Note to the PostSharp team, this ticket is being tracked in our dashboard under ID TP-33361.
I see - well, nonetheless, as I sit here deleting broad swaths of telemetry capture code that I simply don't need anymore, I'm most curious to see just how many lines I've actively deleted that Metalama will build back (and in much greater number with perfect consistency).
Ok it's going to be a bit trickier because we can only estimate the code we generate, not the code you are able to delete. It's not always the same because Metalama does not always generate optimal or idiomatic code.
No, that's entirely understandable. Just being able to view a metric of how many lines of code are in and are generated in each project and solution would be fantastic.
You already capture telemetry that indicates how many lines of code aren't necessary to be typed as a result of using aspects. I would propose that you add some way (e.g. a modal window in VS at the very least) so that developers can see that information themselves (without counting the current lines, applying a divorce, counting the lines and then reverting the divorce).
I'm just curious about my own statistics (which seem higher than the advertised numbers) and especially since you have a free tier, this would provide excellent material to developers eager to convince their managers of the value of Metalama with a practical value against their own code base.
Thanks for the consideration!
The text was updated successfully, but these errors were encountered: