Skip to content

edit lexicon style guide so that all union variants must be object or… #128

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
s-adamantine merged 1 commit into from
Jan 23, 2026
Merged

edit lexicon style guide so that all union variants must be object or… #128

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion LEXICON_STYLE_GUIDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ This document summarizes the ATProto Lexicon Style Guide rules that are checked
- **Primitives**: Use appropriate primitive types (string, integer, boolean)
- **Formats**: Apply format constraints (datetime, uri, cid, did, etc.)
- **Refs**: Use refs for reusable types and relationships
- **Unions**: Use unions when a property can be one of several types
- **Unions**: Use unions when a property can be one of several types. All variants in a union must be object or record types (strings/numbers are not allowed directly in unions by ATProto spec).

#### Constraints

Expand Down