Skip to content

Add porting guide for users coming from orjson#1007

Merged
Siyet merged 5 commits intomainfrom
642-orjson-porting-guide
Apr 12, 2026
Merged

Add porting guide for users coming from orjson#1007
Siyet merged 5 commits intomainfrom
642-orjson-porting-guide

Conversation

@Siyet
Copy link
Copy Markdown
Collaborator

@Siyet Siyet commented Apr 9, 2026

Reopening #995 (auto-closed when fork was deleted).

Summary

  • Add docs/porting-from-orjson.rst covering API mapping, option equivalents, typed decoding, error handling, and features without direct equivalent
  • Add page to toctree in docs/index.rst

Closes #642

Note: @ofek suggested restructuring this into a dedicated "Porting" docs section to accommodate future guides (e.g. Pydantic). Happy to rework if that's the preferred approach.

Cover API mapping, option equivalents, typed decoding, error handling,
and features without direct equivalent.

Closes #642
@ofek
Copy link
Copy Markdown
Collaborator

ofek commented Apr 9, 2026

It looks like Pydantic restructured their site to have documentation in the following format, one for each of their libraries:

https://pydantic.dev/docs/(validation|ai|logfire)/

@Siyet Siyet requested a review from jcrist April 10, 2026 07:32
@Siyet
Copy link
Copy Markdown
Collaborator Author

Siyet commented Apr 10, 2026

The failing build job here is unrelated to this PR: it's the link checker tripping on the Pydantic docs redirect (docs.pydantic.dev/latest/pydantic.dev/docs/validation/...), which is fixed in #1008. Once #1008 lands and this branch is rebased, CI should go green.

@Siyet Siyet self-assigned this Apr 12, 2026
@Siyet Siyet added the documentation Improvements or additions to documentation label Apr 12, 2026
aleksandr.tseluyko added 3 commits April 12, 2026 21:51
- Move docs/porting-from-orjson.rst to docs/porting/orjson.rst
- Add docs/porting/index.rst as a landing page for future guides
- Add "Porting" toctree section in docs/index.rst
- Fix cross-references for the new file location
- Fix incorrect workarounds in "Features with no direct equivalent":
  OPT_OMIT_MICROSECONDS, OPT_PASSTHROUGH_DATACLASS,
  OPT_PASSTHROUGH_SUBCLASS
- Clarify pretty-printing two-step process
Both orjson and msgspec encode naive datetimes identically by default
(without timezone). OPT_NAIVE_UTC is an opt-in flag, not the default.
@Siyet Siyet merged commit 0e29058 into main Apr 12, 2026
1 check passed
@Siyet Siyet mentioned this pull request Apr 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Porting guide for users coming from orjson

2 participants