Julien Gautier
adb4d35274
webpack-cli build --node-env=production failed on two issues that
ts-jest's --transpile-only didn't surface:
1. portal-bff TS2454 in user-scopes.service.ts:221 — TypeScript
couldn't see the switch on `kind` as exhaustive, so `let exists:
boolean` was flagged as "used before assigned". The narrowing on
VALUE_BEARING_KINDS.has(kind) doesn't propagate through Set.has
(only Array.includes / type-guards do). Initialise `exists =
false` so it's definitely assigned regardless of switch path;
semantically safe — a non-value-bearing kind that reaches the
switch (shouldn't happen by construction) leaves exists=false and
the next `if (!exists)` throws the same friendly "does not match"
message.
2. portal-admin missing translation: route.user-scopes.title was
declared in app.routes.ts but never added to messages.fr.xlf.
@angular/localize build target requires every $localize id to
have a target in the active locale. Added the trans-unit for the
FR locale ("Périmètres utilisateur — Administration APF Portal").
Local: nx run-many -t build --projects=portal-bff,portal-admin
passes on both.
49 lines
2.3 KiB
XML
49 lines
2.3 KiB
XML
<?xml version="1.0" encoding="UTF-8" ?>
|
||
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2">
|
||
<file source-language="en" target-language="fr" datatype="plaintext" original="ng2.template">
|
||
<body>
|
||
<!-- app -->
|
||
<trans-unit id="app.skipLink" datatype="html">
|
||
<source>Skip to main content</source>
|
||
<target>Aller au contenu principal</target>
|
||
</trans-unit>
|
||
|
||
<!-- route -->
|
||
<trans-unit id="route.home.title" datatype="html">
|
||
<source>APF Portal Admin</source>
|
||
<target>Administration APF Portal</target>
|
||
</trans-unit>
|
||
<trans-unit id="route.audit.title" datatype="html">
|
||
<source>Audit log — APF Portal Admin</source>
|
||
<target>Journal d’audit — Administration APF Portal</target>
|
||
</trans-unit>
|
||
<trans-unit id="route.users.title" datatype="html">
|
||
<source>Users — APF Portal Admin</source>
|
||
<target>Utilisateurs — Administration APF Portal</target>
|
||
</trans-unit>
|
||
<trans-unit id="route.user-scopes.title" datatype="html">
|
||
<source>User scopes — APF Portal Admin</source>
|
||
<target>Périmètres utilisateur — Administration APF Portal</target>
|
||
</trans-unit>
|
||
<trans-unit id="route.profile.title" datatype="html">
|
||
<source>Profile — APF Portal Admin</source>
|
||
<target>Profil — Administration APF Portal</target>
|
||
</trans-unit>
|
||
|
||
<!-- page.home -->
|
||
<trans-unit id="page.home.title" datatype="html">
|
||
<source> APF Portal Admin </source>
|
||
<target> Administration APF Portal </target>
|
||
</trans-unit>
|
||
<trans-unit id="page.home.intro" datatype="html">
|
||
<source> Administrative back-office for the APF Portal. The first functional modules — content management, menu administration, user list, audit log viewer — land in upcoming PRs per ADR-0020. </source>
|
||
<target> Back-office d’administration pour le portail APF. Les premiers modules fonctionnels — gestion de contenu, gestion du menu, liste des utilisateurs, visualiseur d’audit log — arrivent dans les PRs à venir conformément à l’ADR-0020. </target>
|
||
</trans-unit>
|
||
<trans-unit id="page.home.status" datatype="html">
|
||
<source> Skeleton — coming soon </source>
|
||
<target> Squelette — bientôt disponible </target>
|
||
</trans-unit>
|
||
</body>
|
||
</file>
|
||
</xliff>
|