Legacy MVC metadata cleanup?

Hi Francesca Shiekh , Happy new year!!

I was discussing this with engineering and got few suggestions for you:

• Much of what is in that folder is BWC-related, and not relevant to Sidecar modules. However not all of it is.
  • As one example, dependencydef.php applies to Sidecar as well, and deleting that will affect SugarLogic rules for the module: https://support.sugarcrm.com/documentation/sugar_developer/sugar_developer_guide_13.3/a[…]tecture/sugar_logic/dependency_actions/setpanelvisibility/
• You can move those metadata folders out of sugar working directory. and do QRR, and test out, then wait couple of months before permanently delete those folders.
• Sugar has moved away from BWC over the years but few things are still there as legacy code
  • For example, few pieces of administration panel or rarely used views
  • If you use those "rarely used views", you'd want to keep that particular folder for that module

Note: Make sure you backup you Sugar folder before you delete anything and QRR just in case you'd need to revert them.

Thank you Rafael Fernandes , I assume that at some point there will be a cleanup of unnecessary code during an upgrade process.

Francesca Shiekh I don't believe we can do that automatically even when we "cleanup" our core code base as files can be used by customizations, unfortunately that'd be a manual work as far as I can tell.

I was told that our professional services team could assist on a paid engagement if that interests you.

Francesca Shiekh I don't believe we can do that automatically even when we "cleanup" our core code base as files can be used by customizations, unfortunately that'd be a manual work as far as I can tell.

I was told that our professional services team could assist on a paid engagement if that interests you.

Good to know, thanks!