You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Developing means to debug. Currently debugging an UI5 can mean to get a lot of messages that are not really related to my code. For instance, UI5 standard coding related to an OData call is part of the console output.
Finding out what part of the log is part of my own coding is not as easy as it could be. Disabling completely the logging for the standard UI5 coding is not an option, as the log messages can still provide value.
Describe the solution you'd like
I'd like to have support for x_google_ignoreList. Controlled via a new parameter. The list should include all ( or some, configurable) UI5 libraries / code that are not part of the UI5 app. The ignoreList should be dynamically maintend by the ui5 tooling component that provides the UI5 library. This way the configuration is only applied in the local dev environment.
Describe alternatives you've considered
The x_google_ignoreList values can also be manually set by the developer in the Chrome DevTools. In the settings, the ignore list can be custom configured. Adding the value /resources* adds all UI5 libs loaded to the ignore list. This greys out any log message caused by UI5. In case adding x_google_ignoreList to the source map is not possible, maybe the UI5 documentation can be enhanced to add this information.
Is your feature request related to a problem? Please describe.
Developing means to debug. Currently debugging an UI5 can mean to get a lot of messages that are not really related to my code. For instance, UI5 standard coding related to an OData call is part of the console output.
request | @ | datajs.js:2592
invokeRequest | @ | datajs.js:1615
odata.request | @ | datajs.js:7957
(anonym) | @ | ODataMetadata.js:255
ODataMetadata._loadMetadata | @ | ODataMetadata.js:193
Component._createManifestModels | @ | Component.js?eval:1951
Finding out what part of the log is part of my own coding is not as easy as it could be. Disabling completely the logging for the standard UI5 coding is not an option, as the log messages can still provide value.
Describe the solution you'd like
I'd like to have support for x_google_ignoreList. Controlled via a new parameter. The list should include all ( or some, configurable) UI5 libraries / code that are not part of the UI5 app. The ignoreList should be dynamically maintend by the ui5 tooling component that provides the UI5 library. This way the configuration is only applied in the local dev environment.
Describe alternatives you've considered
The x_google_ignoreList values can also be manually set by the developer in the Chrome DevTools. In the settings, the ignore list can be custom configured. Adding the value /resources* adds all UI5 libs loaded to the ignore list. This greys out any log message caused by UI5. In case adding x_google_ignoreList to the source map is not possible, maybe the UI5 documentation can be enhanced to add this information.
Additional context
https://developer.chrome.com/articles/x-google-ignore-list/
The text was updated successfully, but these errors were encountered: