When progenitor generates types, it adds a <details> JSON goes here </details> blob in the top-level structure or enum comment. That JSON blob trips the rust-documentation lint, seemingly due to having square brackets not followed by parens, preventing composition with downstream APIs whose structures are generated by progenitor.
A workaround for this is to use replace in the progenitor generate_api! macro to prevent these generated comments from coming into play.
When progenitor generates types, it adds a
<details> JSON goes here </details>blob in the top-level structure or enum comment. That JSON blob trips the rust-documentation lint, seemingly due to having square brackets not followed by parens, preventing composition with downstream APIs whose structures are generated by progenitor.A workaround for this is to use
replacein the progenitorgenerate_api!macro to prevent these generated comments from coming into play.