@podlite/schema 0.0.39 → 0.0.41

package/CHANGELOG.podlite

@@ -2,6 +2,15 @@
 
 =head1 Upcoming
 
+=head1 0.0.41
+
+=item expose C<attributesOnly> as an additional PEG start rule for parsing a stand-alone configuration-info fragment (e.g. C< :line-numbers :caption<Example>>). Reuses the existing C<attributes> grammar rule — no shadow parser
+=item add C<parseAttributes(src)> helper that returns an array of config items from a configuration-info string. Empty or malformed input returns an empty array (graceful degradation per Specification.pod6 §2380-2383). Primary consumer: C<@podlite/markdown> fenced-code-attribute parsing
+
+=head1 0.0.40
+
+=item recognise the C<header> MIME parameter (RFC 4180 §3) on C<:mime-type> for CSV/TSV C<=data> blocks. When the C<=data> block declares C<:mime-type<'text/csv; header=present'>> (or the same with C<text/tab-separated-values>), C<=table data:X> marks the first row as C<:header>, which renders as C<<th>>/C<<thead>> in HTML and JSX. Default C<absent> preserves the previous behaviour. The MIME-type parser also accepts other parameters (e.g. C<charset>) without disturbing type matching. Spec: podlite-specs#25
+
 =head1 0.0.39
 
 =item resolve C<=table data:<key>> as CSV from a C<=data :mime-type<text/csv>> block (spec §1672) — table content is replaced with C<=row>/C<=cell> structure parsed per RFC 4180 (comma delimiter, C<"...">  quoted fields with C<""> escape). Spec §1672 does not define how to mark a header in CSV-sourced tables; authors who need a header row should use a structured table with C<=begin row :header> or a Markdown GFM table. C<file:<path>> scheme is left unresolved for host-driven readers