Yes please :) I was about to suggest the same thing. 

If the AI mentor displays this information, it will be more beneficial for the development team. 

Hi everyone!
Related question, think there would be a few kinds of deprecated usages, with different likely analysis approaches. Few different dimensions, for example.

Is the deprecated element only referenced but not used? or actually in use? Does this change relevance/importance?

Is this more relevant for references pending already refreshed and 1cp done, where the deprecated marker is now visible on consumer module? Or is more important to flag deprecated element usages, even if the consumer did not refresh the dependency and the deprecate marker is not visible on studio yet?

Hope this makes sense :) If anyone has thoughts. 

thanks!

Rui

I think both used and not used but only referenced are usefull.

Or split it and add 2 new things to AIMentor

• DEPRECATED_ usage
• Unused dependencies of any kind.

I agree with @Lode Desplancke , splitting will be better

Good @Fontinha,

This can really be a good support point in controlling technical debts.

And I also support the contribution of @Lode Desplancke.

+1

Your idea is useful ideas. This will be helpful for developers.

I agree with this suggestion. Considering applications that use deprecated elements as technical debt is a smart move to improve maintainability. It will help us prioritize fixes and ensure the AI Mentor platform stays modern and efficient.