Skip to Content (Press Enter)
Back to Ideas
11
Like
Follow Idea
Manage Unused Public Dependencies
413Views
6Comments
New
Service Studio


Create an option to set unused public actions/entities/etc to No. 

It could check other modules and if the dependency was not used on any module, set Public to No.

Setting Public to No also helps to identify never used elements and keep the producer module clean.


05 Mar 2021
Copy link to comment

Or, the unused user action warning (TrueChange) should also check the dependencies of other modules.


08 Mar 2021
Copy link to comment

This could be interesting if we could have an option to see those dependencies, and bulk edit those which ones we want to change the visibility .

11 Mar 2021
Copy link to comment

I am editing this post.

This feature should only list the unused dependencies and leave to the user the decision to keep it public or not.

11 Mar 2021
Copy link to comment

If the warning applies also to the dependencies of other modules, you don't need to do extra action to check the unused public dependencies.


11 Mar 2021
Copy link to comment

Combining that list with a bulk edit would be a killer feature. Imagine a Search Other Modules screen, or a similar one, with an added checkbox and some buttons to bulk edit the selection.


11 Mar 2021
Copy link to comment

This could also be part of Architecture Dashboard issues.

12 Mar 2021
Copy link to comment
Changed the category to
Service Studio
14 Jun 2021
Copy link to comment