QUICKSTART: narray typo

merge-requests/23/head
Michał 'rysiek' Woźniak 2023-01-28 18:07:14 +00:00
rodzic f0a21dc949
commit edd7a0c2ec
1 zmienionych plików z 1 dodań i 1 usunięć

Wyświetl plik

@ -61,7 +61,7 @@ Let's unpack this:
- The `plugins` key contains an array of objects.\ - The `plugins` key contains an array of objects.\
Each object defines configuration for a plugin. For simplest plugins, the minimal configuration is just the name of the plugin. Based on the name `service-worker.js` establishes which file to load for a given plugin — in this case, it will be `./plugins/fetch/index.js` (relative to where `service-worker.js` script is located). Each object defines configuration for a plugin. For simplest plugins, the minimal configuration is just the name of the plugin. Based on the name `service-worker.js` establishes which file to load for a given plugin — in this case, it will be `./plugins/fetch/index.js` (relative to where `service-worker.js` script is located).
- The `loggedComponents` key is a narray of strings.\ - The `loggedComponents` key is an array of strings.\
It lists the components whose logs should be visible in the deveoper console in the browser. The `service-worker.js` script logs messages as the "service-worker" component, the `fetch` plugin as (you guessed it!) "fetch".\ It lists the components whose logs should be visible in the deveoper console in the browser. The `service-worker.js` script logs messages as the "service-worker" component, the `fetch` plugin as (you guessed it!) "fetch".\
We want the log messages visible for both of them, just so that we know what's going on. In a production environment we would perhaps want to limit the log messages to only some components. We want the log messages visible for both of them, just so that we know what's going on. In a production environment we would perhaps want to limit the log messages to only some components.