$ the-wire · showcase
to_markdown fixes broken code spans, Ractor schema cache simplified
By RepoJournal · Filed · About Rails · Composed from the cited sources · methodology
Action Text's Markdown conversion stops leaking sanitized links when code spans sit in table cells, while rails/rails retires the hand-rolled proxy schema cache in favor of a bound schema reflection.
Fix `to_markdown` code spans broken by tables and adjacent code rails/rails
`to_markdown` writes `<code>` and `<pre>` text unescaped and relies on the code span delimiter to stop renderers parsing it as Markdown, and some inputs break that delimiter so a link `visit_a` would have dropped comes through as a live link. Table-cell code spans whose text starts with two or more spaces, a tab, VT or FF are the reproducer.
Use a BoundSchemaReflection for the Ractor proxy pool's schema cache rails/rails
The Ractor adapter's schema cache proxy was implemented too cleverly; it now delegates to a bound schema reflection and drops the custom class and its bound-cache machinery. Relevant if you run the Ractor-isolated adapter and touch schema cache behavior.
Bump 1.5.1 rails/lemans
rails/lemans tags 1.5.1, bundling the reporting work below into a cut.
+ lemans report --skip-invalid --hide-columns rails/lemans
`lemans report` gains `--skip-invalid` and `--hide-columns`, so a run with bad entries no longer has to be cleaned up before you get a report, and wide tables can be trimmed.
+ lemans report -S with multiple columns rails/lemans
The `-S` flag now accepts multiple columns, and report output adds features and progress sections.
