From 8f99f7115675c8ed3f1ade5aba8128ba7bc8a3a2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ivar=20Conradi=20=C3=98sthus?= Date: Thu, 4 Feb 2021 22:10:31 +0100 Subject: [PATCH] chore: fix broken link in docs fixes: https://github.com/Unleash/unleash.github.io/issues/6 --- docs/configuring-unleash.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-unleash.md b/docs/configuring-unleash.md index a740d022d4..0391e037f7 100644 --- a/docs/configuring-unleash.md +++ b/docs/configuring-unleash.md @@ -47,7 +47,7 @@ unleash.start(unleashOptions); - `unsecure` - (default) will use simple cookie based authentication. UI will require the user to specify an email in order to use unleash. - `custom` - use this when you implement your own custom authentication logic. - **ui** (object) - Set of UI specific overrides. You may set the following keys: `headerBackground`, `environment`, `slogan`. -- **getLogger** (function) - Used to register a [custom log provider](#How do I configure the log output). +- **getLogger** (function) - Used to register a [custom log provider](#how-do-i-configure-the-log-output). - **eventHook** (`function(event, data)`) - If provided, this function will be invoked whenever a feature is mutated. The possible values for `event` are `'feature-created'`, `'feature-updated'`, `'feature-archived'`, `'feature-revived'`. The `data` argument contains information about the mutation. Its fields are `type` (string) - the event type (same as `event`); `createdBy` (string) - the user who performed the mutation; `data` - the contents of the change. The contents in `data` differs based on the event type; For `'feature-archived'` and `'feature-revived'`, the only field will be `name` - the name of the feature. For `'feature-created'` and `'feature-updated'` the data follows a schema defined in the code [here](https://github.com/Unleash/unleash/blob/master/lib/routes/admin-api/feature-schema.js#L38-L59). See an example [here](./guides/feature-updates-to-slack.md). - **baseUriPath** (string) - use to register a base path for all routes on the application. For example `/my/unleash/base` (note the starting /). Defaults to `/`. Can also be configured through the environment variable `BASE_URI_PATH`. - **secureHeaders** (boolean) - use this to enable security headers (HSTS, CSP, etc) when serving Unleash from HTTPS. Can also be configured through the environment variable `SECURE_HEADERS`.