New reference documentation from Pydantic#222
Conversation
e6ea8d0 to
abd354e
Compare
b6bf09d to
fa2e953
Compare
fa2e953 to
0b290b7
Compare
0b290b7 to
fe96c27
Compare
e957a48 to
5cdf6c4
Compare
056ef89 to
097bf05
Compare
2862cbe to
d39b96b
Compare
090537e to
c4df84e
Compare
dada7c1 to
780b023
Compare
Fix sidebar
Include model-level validation rules
🚀 Overture Maps docs branch preview deployed!You can review your changes at https://staging.overturemaps.org/docs/pr/222/index.html ♻️ Last refreshed: 2026-02-26T00:36:53Z |
Jennings Anderson (jenningsanderson)
left a comment
There was a problem hiding this comment.
🚀
Include various minor improvements
27232c9 to
9b563cf
Compare
Super-linter summary
Super-linter detected linting errors For more information, see the GitHub Actions workflow run Powered by Super-linter MARKDOWNNATURAL_LANGUAGE |
Super-linter summary
Super-linter detected linting errors For more information, see the GitHub Actions workflow run Powered by Super-linter MARKDOWNNATURAL_LANGUAGE |
Super-linter summary
Super-linter detected linting errors For more information, see the GitHub Actions workflow run Powered by Super-linter MARKDOWNNATURAL_LANGUAGE |
Super-linter summary
Super-linter detected linting errors For more information, see the GitHub Actions workflow run Powered by Super-linter MARKDOWNNATURAL_LANGUAGE |
Super-linter summary
Super-linter detected linting errors For more information, see the GitHub Actions workflow run Powered by Super-linter MARKDOWNNATURAL_LANGUAGE |
Super-linter summary
Super-linter detected linting errors For more information, see the GitHub Actions workflow run Powered by Super-linter MARKDOWNNATURAL_LANGUAGE |
Dana Bauer (danabauer)
left a comment
There was a problem hiding this comment.
This is a beast.
Moving to Pydantic!
This PR updates and simplifies the docs to show easier, table-based schema docs.
Enhancements to
docscode:/schema/reference Updates:
Today, everything available under docs.overturemaps.org/schema lives here: https://github.com/OvertureMaps/schema/tree/dev/docs/schema. When docusaurus builds the docs, it fetches the .mdx, schema, and examples from the schema repo. This is a lot of moving parts and kind of ugly.
This PR removes that requirement in favor of simple, machine-readable markdown files that can be self-generated by the schema and used by documentation.
See https://staging.overturemaps.org/docs/pr/222/schema/reference/address/ for an example of how we envision these reference docs rendering.
Next Steps:
Before this is ready to merge, we need to develop the ability for the schema to create self-describing documentation with examples as markdown files, example:
The full schema should be a series of markdown files nested by theme/type that have relative links. We can adjust the
SmartTablecomponent as necessary to make the links work — but the markdown should be a nice, standalone set of files.If the examples that were embedded were actually derived from the examples in the schema repository after being validated by the schema itself, that would be best case scenario.
Once this ability exists, we can update this repository to fetch these markdown files (or checkout schema and build the markdown as part of the publish). The idea is these files can be dropped directly into
docs/schemato power this part of the documentation.Docs Preview
Example:
