Add markdown formatter to docs output - #104
Open
oliver-kriska wants to merge 1 commit into
Open
Conversation
Co-authored-by: Oliver Kriska <oliver@ideax.sk>
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.
ex_doc v0.40.0 (January 2026) added a Markdown formatter and generates
llms.txtby default. Because this project pins an explicitformatters:list, the new default never applies, so the docs build correctly but are not retrievable as markdown.This adds
"markdown"to the existing list. The HTML output is unchanged, and no other formatter is added or removed.After the next docs publish,
hexdocs.pm/x509/llms.txtwill start resolving and individual pages will become available as.md.Verification:
mix docspasses and emitsdoc/llms.txtplus Markdown pages.mix format --check-formattedpasses.mix compile --warnings-as-errorspasses.mix test --include opensslhas one pre-existing, date-sensitive failure: the EdDSA certificate fixture is expired ({:bad_cert, :cert_expired}attest/x509/certificate_test.exs:218). The same targeted test fails unchanged on the unmodified upstream branch.This change was generated from Elixir's retrieval gap is a rollout problem, not an access problem.
Note: this package's currently published docs were built with an older ex_doc, so the markdown output will appear after the next
mix hex.publish docs— no rush, just flagging that the merge alone won't change hexdocs.— Oliver’s AMP