1
0
mirror of https://github.com/Unleash/unleash.git synced 2025-11-24 20:06:55 +01:00
unleash.unleash/frontend
Thomas Heartman b33abf036b
chore: configure the 'maintenanceMode' flag to accept variants (#10956)
Configure the `maintenanceMode` flag type to be `boolean | Variant` and
update the env parsing to allow passing strings from the env.

The [first
impl](3bbfc9e681)
required you to set a full, variant -- stringified as json -- in the
env, but this is both error-prone and not very user friendly.
Additionally, the name of the variant isn't really important, and if
you're passing a string, you probably want it to be true.

As such, the [second
impl](c38357baa4)
updates the env parsing to read the full string value into a
pre-formatted variant if it's not parseable as a boolean.

As such, to set a custom message, you can now do:

```sh
UNLEASH_EXPERIMENTAL_MAINTENANCE_MODE='Custom message from plain env var string' yarn dev
```

With the [updates to the
UI](https://github.com/Unleash/unleash/pull/10961), it'll look a little
something like this:

<img width="388" height="64" alt="image"
src="https://github.com/user-attachments/assets/6b8a174b-d75f-4748-8f1a-1ad4ebce2073"
/>

## Rationale

This allows locking down Unleash instances with a custom message.
Previously, you'd have to use both maintenance mode and a custom banner
for this, but that requires more work to set properly and it shows two
banners, when you really only want the one.
2025-11-11 12:52:49 +01:00
..
.yarn/releases chore(build): Bump Yarn to 4.10.3 (#10865) 2025-10-27 12:58:24 +01:00
cypress chore!: removing userId strategy for new installations of Unleash (#9800) 2025-06-04 09:30:13 +02:00
public chore: simplify serving of static openapi assets (#10046) 2025-05-28 19:14:55 +02:00
scripts fix: orval for ESM (#10086) 2025-06-05 10:40:58 +00:00
src chore: configure the 'maintenanceMode' flag to accept variants (#10956) 2025-11-11 12:52:49 +01:00
.editorconfig
.gitignore
.npmignore
.nvmrc chore(deps): update node.js to v22 (#9487) 2025-05-14 10:31:18 +00:00
.yarnrc.yml chore(build): Bump Yarn to 4.10.3 (#10865) 2025-10-27 12:58:24 +01:00
check-imports.rc
cypress.config.ts feat: Unleash v7 ESM migration (#9877) 2025-05-14 09:47:12 +02:00
cypress.d.ts
index.html
index.js feat: Unleash v7 ESM migration (#9877) 2025-05-14 09:47:12 +02:00
mise.toml feat: Unleash v7 ESM migration (#9877) 2025-05-14 09:47:12 +02:00
orval.config.ts fix: orval for ESM (#10086) 2025-06-05 10:40:58 +00:00
package.json chore(build): Bump Yarn to 4.10.3 (#10865) 2025-10-27 12:58:24 +01:00
README.md
tsconfig.json feat: Unleash v7 ESM migration (#9877) 2025-05-14 09:47:12 +02:00
tsconfig.node.json feat: Unleash v7 ESM migration (#9877) 2025-05-14 09:47:12 +02:00
vercel.json
vite.config.mts
yarn.lock chore(deps): bump validator from 13.12.0 to 13.15.20 in /frontend (#10877) 2025-10-28 09:37:52 +01:00

frontend

This directory contains the Unleash Admin UI frontend app.

Run with a local instance of the unleash-api

Refer to the Contributing to Unleash guide for instructions. The frontend dev server runs (in port 3000) simultaneously with the backend dev server (in port 4242):

yarn install
yarn dev

Run with a sandbox instance of the Unleash API

Alternatively, instead of running unleash-api on localhost, you can use a remote instance:

cd ./frontend
yarn install
yarn run start:sandbox

Running end-to-end tests

We have a set of Cypress tests that run on the build before a PR can be merged so it's important that you check these yourself before submitting a PR. On the server the tests will run against the deployed Heroku app so this is what you probably want to test against:

yarn run start:sandbox

In a different shell, you can run the tests themselves:

yarn run e2e:heroku

If you need to test against patches against a local server instance, you'll need to run that, and then run the end to end tests using:

yarn run e2e

You may also need to test that a feature works against the enterprise version of unleash. Assuming the Heroku instance is still running, this can be done by:

yarn run start:enterprise
yarn run e2e

Generating the OpenAPI client

The frontend uses an OpenAPI client generated from the backend's OpenAPI spec. Whenever there are changes to the backend API, the client should be regenerated:

For now we only use generated types (src/openapi/models). We will use methods (src/openapi/apis) for new features soon.

yarn gen:api
rm -rf src/openapi/apis

clean up src/openapi/index.ts imports, only keep first line export * from './models';

This script assumes that you have a running instance of the enterprise backend at http://localhost:4242. The new OpenAPI client will be generated from the runtime schema of this instance. The target URL can be changed by setting the UNLEASH_OPENAPI_URL env var.

Analyzing bundle size

npx vite-bundle-visualizer in the root of the frontend directory