1
0
mirror of https://github.com/Unleash/unleash.git synced 2025-10-04 11:17:02 +02:00
unleash.unleash/frontend
Thomas Heartman cb4beb71ac
Chore(1 3895)/small input tweaks (#10316)
Doesn't clear the value from the constraint input value popover if you
close it and then re-open. In other words, if you accidentally click
out, you don't lose your progress. Instead, the popover will open again,
with the value you had when you closed it highlighted (so that it's easy
to type over if you want to):

<img width="452" alt="image"
src="https://github.com/user-attachments/assets/d86aa00e-4956-40a8-8fea-e75be5d5425b"
/>

The reason I'm changing this now is because I noticed that the error
wasn't cleared correctly when the popover was closed. If we do it this
way instead, then that makes sense, because you can still see the value.
This is also how the single-value popover has worked forever.

From some quick testing, the single value popover still works as
expected:
<img width="562" alt="image"
src="https://github.com/user-attachments/assets/9041a922-b055-4310-ab60-93ad219981a4"
/>


As a side note: I'm adding a comment to anyone coming after as to why
focus handling on escape doesn't work correctly on the single value
button. I was about to go down a rabbit hole on that before I read my
own comment on the previous PR. So I thought I'd put that here too.
2025-07-04 14:57:52 +02:00
..
.yarn/releases chore: Bumped Yarn to 4.9.2 (#10126) 2025-06-12 12:01:43 +02: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(1 3895)/small input tweaks (#10316) 2025-07-04 14:57:52 +02:00
.editorconfig
.gitignore
.npmignore
.nvmrc chore(deps): update node.js to v22 (#9487) 2025-05-14 10:31:18 +00:00
.yarnrc.yml chore: Bumped Yarn to 4.9.2 (#10126) 2025-06-12 12:01:43 +02: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 feat: use Unleash React SDK in Admin UI (#9723) 2025-04-10 08:26:30 +02:00
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 Feat: impact metrics grid layout (#10253) 2025-07-03 09:09:03 +00: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 Feat: impact metrics grid layout (#10253) 2025-07-03 09:09:03 +00: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