Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Add x_google_ignoreList support

Abierto
  • ¿Algo no está bien?
#858 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
javascript
Área
build-system, tooling

Línea de trabajo

Start by reading the linked Chrome DevTools x_google_ignore_list documentation and tracing how the UI5 tooling component provides libraries and generates source maps. Define how a configurable parameter would maintain UI5 library entries only in local development, and verify that the resulting source maps produce the intended ignored-library behavior.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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/

Lenguaje dominante
JavaScript
Estrellas
511
Forks
83
Merge medio
1 d 5 h
PR fusionados (30 d)
50

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de UI5/cli

Todos los issues de UI5/cli

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.