Skip to content

Commit d9a2601

Browse files
committed
fix: more
1 parent eb5497e commit d9a2601

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -511,7 +511,7 @@ For example:
511511
}]
512512
```
513513

514-
You can conveniently create a filter definition without having to write it by hand by first saving a filter in the data browser, then exporting the filter definition under _App Settings > Export Class Preferences_.
514+
You can conveniently create a filter definition without having to write it by hand by first saving a filter in the data browser, then exporting the filter definition under *App Settings > Export Class Preferences*.
515515

516516
### Scripts
517517

@@ -646,7 +646,7 @@ const dashboard = new ParseDashboard({
646646
> This feature can make it more difficult to push dashboard updates to users. Enabling the resource cache will start a browser service worker that caches dashboard resources locally only once. As long as the service worker is running, it will prevent loading any dashboard updates from the server, even if the user reloads the browser tab. The service worker is automatically stopped, once the last dashboard browser tab is closed. On the opening of the first dashboard browser tab, a new service worker is started and the dashboard resources are loaded from the server.
647647
648648
> [!Note]
649-
> For developers: during dashboard development, the resource cache should be disabled to ensure reloading the dashboard tab in the browser loads the new dashboard bundle with any changes you made in the source code. You can inspect the service worker in the developer tools of most browsers. For example in Google Chrome, go to _Developer Tools > Application tab > Service workers_ to see whether the dashboard service worker is currently running and to debug it.
649+
> For developers: during dashboard development, the resource cache should be disabled to ensure reloading the dashboard tab in the browser loads the new dashboard bundle with any changes you made in the source code. You can inspect the service worker in the developer tools of most browsers. For example in Google Chrome, go to *Developer Tools > Application tab > Service workers* to see whether the dashboard service worker is currently running and to debug it.
650650
651651
# Running as Express Middleware
652652

0 commit comments

Comments
 (0)