Skip to content

feat: update VTL editor, align legacy on React 19, add standalone mode - #1238

Open
NicoLaval wants to merge 16 commits into
InseeFr:mainfrom
Making-Sense-Info:feat/update-vtl-editor
Open

feat: update VTL editor, align legacy on React 19, add standalone mode#1238
NicoLaval wants to merge 16 commits into
InseeFr:mainfrom
Making-Sense-Info:feat/update-vtl-editor

Conversation

@NicoLaval

@NicoLaval NicoLaval commented Aug 22, 2026

Copy link
Copy Markdown
Contributor
  • Standalone mode to run without Keycloak/API (in-memory mock, dev:standalone / pnpm standalone, docs updated)
  • Bump @making-sense/antlr-editor to 2.9.4 to fix VTL script validation errors in the UI (empty / partial expressions)
  • Legacy aligned on React 19 with next (Module Federation, Monaco / VTL 2.1)
  • Cleanup: drop enzyme and obsolete specs; small CSS fixes (fonts / Tailwind layers)
  • Next: mock API wiring, VTL editor, and legacy remote follow the same stack
  • Skip SonarCloud/SonarQube CI jobs on fork PRs (no Sonar token); still run on InseeFr pushes and internal PRs

NicoLaval and others added 8 commits August 22, 2026 09:16
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@NicoLaval
NicoLaval force-pushed the feat/update-vtl-editor branch from 8fae188 to 1f5029c Compare August 23, 2026 20:01
Co-authored-by: Cursor <cursoragent@cursor.com>
@NicoLaval
NicoLaval force-pushed the feat/update-vtl-editor branch from 1f5029c to 6f8a9ae Compare August 23, 2026 20:07
@NicoLaval NicoLaval changed the title chore(next): bump antlr-editor and VTL 2.1 stack feat: update VTL editor, align legacy on React 19, add standalone mode Aug 23, 2026
@laurentC35

Copy link
Copy Markdown
Contributor

ça a l'air en good en première lecture !
Le passage à React 19 nous enlèverai une épine du pied !

Cependant, quelques fonctionnalité ne fonctionnent plus:

  • "Voir le detail" d'une question fait cracher l'application (legacy seul ou next & legacy ensemble)
  • De manière générale, le formulaire pour ajouter une Question ne fonctionne pas
  • En mode next+legacy ensemble, la barre permettant l'ajout de Question, Séquence, Boucle & Filtre, Sauvegarde, etc disparait

NicoLaval and others added 7 commits August 24, 2026 09:54
React 19 removes support for defaultProps on function components.
Migrates all ~60 affected components to use default parameter values
directly in destructuring, fixing crashes on "Voir le detail",
the new question form, and the toolbar disappearing in next+legacy mode.

Co-authored-by: Cursor <cursoragent@cursor.com>
redux-form injects `form` via defaultProps on a forwardRef HOC, which
React 19 ignores. Wrap reduxForm so the form name is always provided.

Co-authored-by: Cursor <cursoragent@cursor.com>
connect() containers no longer apply defaultProps under React 19.
Default form name and componentId where the edit form still relied on them.

Co-authored-by: Cursor <cursoragent@cursor.com>
Pass formName/selectorPath from the question form and default them in
the container/component so the tab no longer mounts with undefined paths.

Co-authored-by: Cursor <cursoragent@cursor.com>
Parents often omit these props; container defaultProps no longer apply
under React 19, so FormSection/formValueSelector would get undefined.

Co-authored-by: Cursor <cursoragent@cursor.com>
AssociatedFields, SelectorView, OptionalView, GotoInput and
ListWithInputPanel relied on connect defaultProps that React 19 drops.

Co-authored-by: Cursor <cursoragent@cursor.com>
Avoid crashes when item label, date format or markdown content is missing
after optional props stop being filled by defaultProps.

Co-authored-by: Cursor <cursoragent@cursor.com>
@NicoLaval

Copy link
Copy Markdown
Contributor Author

@laurentC35, thanks for the review.

Root cause: under React 19, defaultProps on function components (and on forwardRef / connect / reduxForm HOCs) are no longer applied.

Fixes:

  • migrate defaultProps to defaults in destructuring
  • add a reduxFormNamed wrapper that passes form explicitly
  • restore defaults / explicit props on containers that still relied on defaultProps

Keep me informed.

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.

2 participants