Skip to content

Release v0.34.0

Choose a tag to compare

@github-actions github-actions released this 08 Aug 21:19
f6f7927

What the gate cannot see. The build gate got teeth in 0.30.0, the commands stopped contradicting each other in 0.31.0 and every silent degradation started reporting itself in 0.32.0. All three work on what verbaly reads at build time, and this version goes after the other half: a catalog that arrives from a CMS after the build, a source file the parser cannot read, and a <br/> inside a rich message that the static HTML and the browser disagree about. Four real bugs, each one a way to ship something wrong with every command green, all of them found by reading the code against the invariants the project had already written down. No breaking changes, no new configuration, no new runtime API.

Highlights

  • A line break inside a rich message no longer doubles in the pre-rendered page. verbaly render wrote <br></br>, which every browser reads as two line breaks, and hydration then replaced them with one. A visible jump on exactly the pages the feature exists to keep still.
  • A catalog with a null value no longer takes the app down at boot. A translation that arrives as null (a CMS field nobody filled, a TMS export) used to crash the instance before the first render. Now the key is skipped, the app runs, and the console says which one it was.
  • verbaly extract, check and doctor survive a file they cannot read. One file with a syntax error used to end the whole run with a position and no file name. Now the file is named, its messages are skipped and every other file is still processed.
  • JSX written in a .js file is extracted like any other source. A React app with components in .js could not run verbaly extract at all: the first tag ended it. This was the most likely first five minutes for a whole class of project.
  • A warning never repeats itself because a number changed. Three warnings still printed the offending value, so a counter walking 0 to N could grow the deduplication set forever. They now name the type instead, and every degradation says which message it came from.

For the full details of this release, see the repository changelog.