Skip to content

[deflag] Deflagration phase 6 — ENABLE_NEW_URL_SCHEME#8133

Open
dglazkov wants to merge 1 commit intomainfrom
deflag-new-url-scheme
Open

[deflag] Deflagration phase 6 — ENABLE_NEW_URL_SCHEME#8133
dglazkov wants to merge 1 commit intomainfrom
deflag-new-url-scheme

Conversation

@dglazkov
Copy link
Collaborator

What

Remove the always-on ENABLE_NEW_URL_SCHEME flag. This flag controlled whether the Visual Editor used pathname-based routing (/app/{driveId}, /edit/{driveId}) or legacy query-parameter routing (?flow=…&mode=…). With the flag always true, the pathname scheme was already unconditional.

Why

The flag is true in every TF environment. The old query-parameter URL generation was dead code. Part of Project Deflagration.

Changes

packages/types

  • deployment-configuration.ts: Removed ENABLE_NEW_URL_SCHEME from ClientDeploymentConfiguration type.

packages/unified-server

  • flags.ts: Removed ENABLE_NEW_URL_SCHEME export.
  • config.ts: Removed from config wiring.

packages/visual-editor

  • urls.ts: Removed enableNewUrlScheme parameter from makeUrl(). Inlined the always-true branch (pathname routing). Removed dead CLIENT_DEPLOYMENT_CONFIG import. The old query-param branches for FLOW and MODE in makeUrl are gone; parseUrl() still handles both schemes for backward compatibility.
  • Tests: Updated urls.test.ts (removed the false-branch makeUrl call from testSymmetrical), simplified router-controller.test.ts (removed CLIENT_DEPLOYMENT_CONFIG import and manual flag toggling in the invalid-flow-ID test).

Testing

  • npm run build:tsc all affected packages ✅
  • npm run test -w packages/visual-editor
  • git grep ENABLE_NEW_URL_SCHEME returns zero hits (excluding project doc)

## What

Remove the always-on `ENABLE_NEW_URL_SCHEME` flag. This flag controlled whether the Visual Editor used pathname-based routing (`/app/{driveId}`, `/edit/{driveId}`) or legacy query-parameter routing (`?flow=…&mode=…`). With the flag always true, the pathname scheme was already unconditional.

## Why

The flag is `true` in every TF environment. The old query-parameter URL generation was dead code. Part of [Project Deflagration](./PROJECT_DEFLAGRATION.md).

## Changes

### `packages/types`
- **`deployment-configuration.ts`**: Removed `ENABLE_NEW_URL_SCHEME` from `ClientDeploymentConfiguration` type.

### `packages/unified-server`
- **`flags.ts`**: Removed `ENABLE_NEW_URL_SCHEME` export.
- **`config.ts`**: Removed from config wiring.

### `packages/visual-editor`
- **`urls.ts`**: Removed `enableNewUrlScheme` parameter from `makeUrl()`. Inlined the always-true branch (pathname routing). Removed dead `CLIENT_DEPLOYMENT_CONFIG` import. The old query-param branches for `FLOW` and `MODE` in `makeUrl` are gone; `parseUrl()` still handles both schemes for backward compatibility.
- **Tests**: Updated `urls.test.ts` (removed the false-branch `makeUrl` call from `testSymmetrical`), simplified `router-controller.test.ts` (removed `CLIENT_DEPLOYMENT_CONFIG` import and manual flag toggling in the invalid-flow-ID test).

## Testing

- `npm run build:tsc` all affected packages ✅
- `npm run test -w packages/visual-editor` ✅
- `git grep ENABLE_NEW_URL_SCHEME` returns zero hits (excluding project doc)
@dglazkov dglazkov enabled auto-merge (squash) March 10, 2026 22:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant