Repository navigation
Conversation
Deploying organicmaps with
|
| Latest commit: |
8b657c3
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://9b031e59.organicmaps.pages.dev |
| Branch Preview URL: | https://fix-translation-metadata-val.organicmaps.pages.dev |
Check reader-visible fields and shared brand invariants before applying the taxonomy-note body exemption. Reject malformed YAML and metadata shapes before translation, model or Telegram requests. Share the header delimiter pattern and restore the Russian news title key. Signed-off-by: Alexander Borsuk <me@alex.bio>
biodranik
force-pushed
the
fix/translation-metadata-validation
branch
from
November 3, 2026 16:34
27362d2 to
8b657c3
Compare
This branch was successfully deployed
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.
Require translations to retain reader-visible metadata fields as non-empty strings, with product names and runtime placeholders preserved. Malformed YAML and non-mapping headers or
extravalues produce explicit errors. The FAQ maintenance-note body exemption requiresrender: falsein both documents; metadata validation runs independently.Share brand checks between body text and metadata, remove an ineffective transliteration-exemption table and duplicate brand entry, and use one delimiter pattern for parsing and translation. Empty headers and headers ending at EOF are recognized consistently. Translation, proofreading and both Telegram commands reject malformed inputs before API/model calls, including malformed linked-page metadata.
Restore the Russian article's
title:key incontent/news/2024-03-22/325/index.ru.md, so its page title and H1 render correctly.Validation:
Organic Maps; body diagnostics are unchanged. These omissions remain visible in the existing report-only corpus check.git diff --checkpass.Created from master. Related to #365's narrower FAQ metadata fix; this PR adds required-field, parser, brand and rendering-policy validation.