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
Copy file name to clipboardExpand all lines: src/core/MIGRATION.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1308,7 +1308,7 @@ This table shows where these uiExports have moved to in the New Platform. In mos
1308
1308
|`hacks`| n/a | Just run the code in your plugin's `start` method. |
1309
1309
| `home` | [`plugins.home.featureCatalogue.register`](./src/plugins/home/public/feature_catalogue) | Must add `home` as a dependency in your kibana.json. |
1310
1310
| `indexManagement` | | Should be an API on the indexManagement plugin. |
1311
-
| `injectDefaultVars` | n/a | Plugins will only be able to "whitelist" config values for the frontend. See [#41990](https://github.com/elastic/kibana/issues/41990) |
1311
+
| `injectDefaultVars` | n/a | Plugins will only be able to allow config values for the frontend. See [#41990](https://github.com/elastic/kibana/issues/41990) |
1312
1312
| `inspectorViews` | | Should be an API on the data (?) plugin. |
1313
1313
| `interpreter` | | Should be an API on the interpreter plugin. |
1314
1314
| `links` | n/a | Not necessary, just register your app via `core.application.register` |
@@ -1387,7 +1387,7 @@ class MyPlugin {
1387
1387
}
1388
1388
```
1389
1389
1390
-
If your plugin also have a client-side part, you can also expose configuration properties to it using a whitelisting mechanism withthe configuration `exposeToBrowser` property.
1390
+
If your plugin also have a client-side part, you can also expose configuration properties to it using the configuration `exposeToBrowser` allow-list property.
0 commit comments