Skip to content

Drop stale migration references and GWT removal leftovers - #25216

Open
totally-not-ai[bot] wants to merge 1 commit into
flow-server-remove-client-enginefrom
flow-client-ts-cleanup-stale-refs
Open

Drop stale migration references and GWT removal leftovers#25216
totally-not-ai[bot] wants to merge 1 commit into
flow-server-remove-client-enginefrom
flow-client-ts-cleanup-stale-refs

Conversation

@totally-not-ai

@totally-not-ai totally-not-ai Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Follow-up to #25210, which removed the GWT client. The comments left behind in the TypeScript client still described work in progress, and a few build/runtime artifacts of the GWT era were still around.

Comment rewording

The port comments in flow-client/src/main/frontend/internal/** described the TS files as being "built alongside the Java version", listed things "not ported yet", promised "contracts satisfied at cutover", justified ES5 bundling with the HtmlUnit-based GwtTests, and referred to callbacks arriving pre-wrapped in $entry from the Java side. None of that is true any more:

  • publishClient.ts claimed it was "not yet wired into the bootstrap" and pointed at a MIGRATION_STRATEGY.md that does not exist in the repository.
  • SimpleElementBindingStrategy.ts said its standalone functions would eventually be assembled into a BindingStrategy<Element> class — a class the same file already defines.
  • ExecuteJavaScriptProcessor.ts described $entry boundaries and ES5 bundling for GwtTests.

The comments are reworded to describe the code as it actually is. References to the GWT original are kept where they explain why something looks the way it does (e.g. "TypeScript port of com.vaadin.client.flow.binding.SimpleElementBindingStrategy"). The Slice N: section headers, which numbered the migration steps, lose the numbering and keep their titles (--- closest-state-node lookups ---, --- attribute binding ---, and so on).

GWT leftovers removed

  • com/google/gwt/dev/js/globals/firefox25.txt — an 872-line GWT compiler resource with nothing left to read it.
  • gwt.version property and the com.google.gwt:gwt-elemental dependencyManagement entry in the root pom.xml; no module depends on GWT any more.
  • ApplicationConstants.CLIENT_ENGINE_PATH, which named a VAADIN/static/client folder that is no longer served or referenced anywhere.
  • SessionCloseLogoutIT no longer whitelists console errors from the removed client engine path; its filter now only allows FlowClient.js messages.

No functional change: comments, an unused resource, unused build configuration, and one unused constant.

API Changes

com.vaadin.flow.shared.ApplicationConstants

// Removed
public static final String CLIENT_ENGINE_PATH // path to the removed GWT client engine folder; no longer served or referenced

@totally-not-ai totally-not-ai Bot changed the title flow client ts cleanup stale refs Port the Flow client engine from GWT/Java to TypeScript and delete the GWT client Aug 13, 2026
@Artur-
Artur- changed the base branch from main to flow-client-ts-console-gating August 13, 2026 13:08
@github-actions

github-actions Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Test Results

 1 346 files  ±0   1 432 suites  ±0   1h 26m 47s ⏱️ +11s
10 659 tests ±0  10 592 ✅ ±0  67 💤 ±0  0 ❌ ±0 
10 978 runs  ±0  10 910 ✅ ±0  68 💤 ±0  0 ❌ ±0 

Results for commit f51a22e. ± Comparison against base commit b09bd07.

♻️ This comment has been updated with latest results.

@Artur-
Artur- force-pushed the flow-client-ts-cleanup-stale-refs branch from a5ba6fc to c6735d1 Compare August 14, 2026 07:59
@Artur-
Artur- changed the base branch from flow-client-ts-console-gating to flow-server-remove-client-engine August 14, 2026 08:01
@totally-not-ai
totally-not-ai Bot force-pushed the flow-client-ts-cleanup-stale-refs branch from c6735d1 to bf2f491 Compare August 16, 2026 09:48
@totally-not-ai totally-not-ai Bot changed the title Port the Flow client engine from GWT/Java to TypeScript and delete the GWT client Replace the GWT client engine with a TypeScript port Aug 16, 2026
@totally-not-ai totally-not-ai Bot changed the title Replace the GWT client engine with a TypeScript port ````markdown Aug 16, 2026
@totally-not-ai totally-not-ai Bot changed the title ````markdown Replace the GWT client engine with the TypeScript client Aug 16, 2026
@totally-not-ai
totally-not-ai Bot force-pushed the flow-client-ts-cleanup-stale-refs branch from b2c830a to 98610ab Compare August 16, 2026 11:46
@totally-not-ai totally-not-ai Bot changed the title Replace the GWT client engine with the TypeScript client feat(flow-client): replace the GWT client engine with a TypeScript client Aug 16, 2026
@github-actions github-actions Bot added +0.0.1 and removed +1.0.0 labels Aug 16, 2026
@vaadin-bot vaadin-bot added +1.0.0 and removed +0.0.1 labels Aug 16, 2026
@totally-not-ai totally-not-ai Bot changed the title feat(flow-client): replace the GWT client engine with a TypeScript client ```` markdown Aug 16, 2026
@totally-not-ai
totally-not-ai Bot force-pushed the flow-client-ts-cleanup-stale-refs branch from 83382a8 to 1beb283 Compare August 16, 2026 12:31
@totally-not-ai totally-not-ai Bot changed the title ```` markdown Replace the GWT client engine with a TypeScript client Aug 16, 2026
@totally-not-ai
totally-not-ai Bot force-pushed the flow-client-ts-cleanup-stale-refs branch from 1beb283 to ef3efdb Compare August 16, 2026 18:17
@totally-not-ai totally-not-ai Bot changed the title Replace the GWT client engine with a TypeScript client I have the complete picture. Here is the API change report. Aug 16, 2026
@totally-not-ai totally-not-ai Bot changed the title I have the complete picture. Here is the API change report. ````markdown Aug 17, 2026
@totally-not-ai
totally-not-ai Bot force-pushed the flow-client-ts-cleanup-stale-refs branch from ef3efdb to 66539d9 Compare August 17, 2026 10:51
@totally-not-ai totally-not-ai Bot changed the title ````markdown chore: drop stale migration references and GWT removal leftovers Aug 17, 2026
@totally-not-ai totally-not-ai Bot changed the title chore: drop stale migration references and GWT removal leftovers ````markdown Aug 17, 2026
@mshabarov
mshabarov requested a review from platosha August 17, 2026 11:46
Follow-up to #25210. The port comments described work in progress -- "built
alongside the Java version", "not ported yet", "contracts satisfied at cutover",
constraints imposed by the HtmlUnit-based GwtTests, and $entry wrappers on the
Java side -- none of which is true now that the GWT client is gone. publishClient
still claimed it was "not yet wired into the bootstrap", pointing at a
MIGRATION_STRATEGY.md that does not exist in the repository, and
SimpleElementBindingStrategy said its functions would be assembled into a class
that it already defines. Reword them to describe the code as it is, keeping the
references to the GWT original where they explain why something looks the way it
does. The "Slice N:" section headers, which numbered the migration steps, lose
the numbering and keep their titles.

Also remove what the GWT deletion left behind: the com/google/gwt/dev/js/globals
resource, the gwt.version property and the gwt-elemental dependencyManagement
entry in the root pom (no module depends on GWT any more), and
ApplicationConstants.CLIENT_ENGINE_PATH, which named a folder that is no longer
served or referenced. SessionCloseLogoutIT no longer allows console errors from
the removed client engine path.
@platosha
platosha force-pushed the flow-client-ts-cleanup-stale-refs branch from 66539d9 to f51a22e Compare August 18, 2026 14:14
@totally-not-ai totally-not-ai Bot changed the title ````markdown Drop stale migration references and GWT removal leftovers Aug 18, 2026
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant