Repository navigation
feat(i18n): english and french events, forms and UI, api errors and logs in english - #133
Merged
Merged
Conversation
The processing events of the api (create, patch, delete, trigger) and the run events of the
worker (log-error, finish-ok, finish-error, disabled) now send { en, fr } titles, written next
to their emitter as in the stack-wide events convention.
The resource title of the run events is the plain processing title, no longer a French sentence.
The topic keys are unchanged.
The events UI reads internalProcess.title: with a name only, the run events showed a generic "Internal process" instead of "Processings Worker".
…er event The trigger-manual default was never used, both calls passed their text.
BatLeDev
marked this pull request as ready for review
November 13, 2026 10:06
- processing and permission schemas: english base keywords, the existing french moved to x-i18n-title / x-i18n-description / x-i18n-label / x-i18n-addItem with a fr value; the permission profiles use short technical titles (ReadProfile, ExecProfile) with the full english text in x-i18n-title.en; no import used the old generated type names - agent-surface golden regenerated for the new schema titles - plugin title, description and group taken in the session language, falling back on the other one (localizedText helper), instead of always fr - localized dayjs formats (lll, L LT) instead of hard-coded french date formats - App.vue sets the document lang from the session; createI18n gets legacy: false and fallbackLocale: 'en' - "Status", "Plugin" and the config section title through <i18n> keys, the auth error of the new processing page too; private-access i18n block lists en first - task progress numbers formatted with the session locale
- registry errors (403 no access, 404 not found, 502 unavailable), the already scheduled / running / requested run errors, the wrong webhook key and inactive processing answers, and the missing plugin source file error are now written in english, like the rest of the logs and errors of the service - unit and api specs asserting on those messages updated, two french comments translated
- worker: the end-of-task diagnosis (JavaScript heap overflow, SIGKILL, unexpected exit) in english; the french user lines are dropped, the user metrics reuse the english ones - worker: run log messages (disabled processing, exhausted time, maintenance interruption, resume, unavailable plugin, log size limit, interrupted / finished run) and the axios retry warning in english - comments and specs that described or asserted the french wording updated (exit-code unit spec, memory-oom, broken-plugin and log-flood api specs)
The error log line fell back to a hardcoded French 'Erreur HTTP' when the response had no statusText; it now uses the httpError key of the component's i18n block. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The OpenAPI document served by GET /processings/:id/api-docs.json was entirely in French, while
the stack's API docs, logs and errors are in English. Rewrite its titles, summaries,
descriptions and parameter texts in English, same structure and keys.
Also put en before fr in the { en, fr } scope descriptions and tag titles.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ssions - "reserved for", "allows triggering" and "Processings API" in the schemas and API docs - localizedText: every non-French session language reads the English text of registry values (de/es/it/pt sessions got French), empty strings fall back on the other language Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Operator precedence made timezoneLabel return the bare timezone (or undefined) instead of " — Timezone: X"; a missing timezone now reads UTC. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
….5.4 The lib releases of the fr/en pass: dates in the session language for non French locales, English byte units, English schema bases, translated search-address and date-match-filter. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Processings goes fr/en: the events, the forms and the UI follow the session language. API errors, logs and the per-processing API document are in English.
{ en, fr }titles. The webhook trigger keeps thetriggertopic key with its own text.resource.titleis the plain processing title, and the worker names itself inoriginator.internalProcess.title(it wasname, so the events UI showed "Internal process").processing/schema.jsandpermission/schema.jsuse an English base with French inx-i18n-*, rendered withxI18n. Plugin titles, descriptions and groups ({ en, fr }values of the registry) read French in French sessions and English in every other session language, each falling back on the other one (ui/src/utils/localized-text.ts, a copy of the reading rule of registry'sui/src/utils/localized.ts). Dates and numbers are localized. The documentlangfollows the session. vue-i18n runs in composition mode withfallbackLocale: 'en'. The last hard-coded strings move to<i18n>blocks.GET /processings/:id/api-docs.json. Specs that asserted the French wording are updated.timezoneLabel); a missing timezone reads UTC.Why: part of the platform-wide fr/en pass (data-fair/catalogs#46, portals, data-fair, simple-directory, events, agents), following the
data-fair-serviceskill (references/events.md,references/i18n.md).Heads-up:
lastRun/nextRuntitles becomerun last run/run next run, which renames the generated types (nothing imports them).