UI5 inspector causes warnings in browser console
Open
Nobody has claimed this yet.
author action
- Dominant language
- JavaScript
- Stars
- 150
- Forks
- 59
- Avg merge
- 6d 22h
- Merged PRs (30d)
- 2
Description
When using the UI5 inspector with current UI5 releases, it raises a number of warnings in the browser console because it uses deprecated APIs. Since these look the same as warnings raised from the running app, it distracts when trying to identify issues with the application. Observed call stacks with SAPUI5 1.126.1:
[Deprecated] UriParameters.mParams must not be accessed. -
log @ Log.js?eval:498
Log.warning @ Log.js?eval:270
get @ UriParameters.js?eval:186
_getFrameworkInformation @ ToolsAPI.js:141
mutation._observer @ main.js:41
Do not use deprecated function 'sap.ui.getVersionInfo' synchronously! Use 'sap/ui/VersionInfo' module's asynchronous .load function instead - Deprecation
log @ Log.js?eval:498
Log.warning @ Log.js?eval:270
sap.ui.getVersionInfo @ Global.js?eval:113
_getFrameworkInformation @ ToolsAPI.js:105
mutation._observer @ main.js:41
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading _getFrameworkInformation in ToolsAPI.js and the mutation observer in main.js, then reproduce the warnings with SAPUI5 1.126.1. Trace the deprecated UriParameters.mParams and synchronous sap.ui.getVersionInfo calls, and verify that framework information is still collected without inspector-generated console warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100