Idea Summary
In the page designer, there is a critical messaging system if I haven't completed all required settings. For example, if I create a new Process and haven't yet entered any PL/SQL Code, it shows the following:
Extend this messaging platform to include non-critical messages.
I see two use cases off the cuff:
- Use of PL/SQL code that is legacy, de-supported or deprecated
- A legacy component or attribute is being used - for example an attribute from a component, but that doesn't appear in new versions; or an item type that was available in previous versions but not available anymore.
For example, the documentation states apex_debug.log_message is deprecated.
I would like to see exposure to any page components/API's being used that are deprecated so I can look to bring them up to date with best practice
Preferred Solution (Optional)
When I use deprecated components, add a new message to the messages dialog. These should appear after all critical errors, and probably would be a yellow colour instead of red, as is common-practice.
This data should also be exposed via a dictionary view to it easily reportable on pages that may be running with “Warnings”.
Not sure how plausible it is, but there's also the issue of capturing this data from compiled packages that are referenced within pages/apps.
Unsure how to handle the badge in the toolbar which shows the message count. It would probably need to distinguish counts from critical to non-critical. IDE's usually have multiple counts for warnings vs errors.