Explain supported property types for Snowtype

[Miranda Wilson (mscwilson)]

Adds a table explaining which schema property types Snowtype supports, in which languages. Apparently objects don't work in Java 😱

Also adds a brief section explaining a name clash limitation in Golang.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	documentation	58663e0	Commit Preview URL Branch Preview URL	Jun 01 2026, 09:42 AM

[netlify]

✅ Deploy Preview for snowplow-docs ready!

Name	Link
🔨 Latest commit	755dcd6
🔍 Latest deploy log	https://app.netlify.com/projects/snowplow-docs/deploys/69e8a742219d090008057f0b
😎 Deploy Preview	https://deploy-preview-1744--snowplow-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 22 (no change from production) Accessibility: 93 (no change from production) Best Practices: 100 (🟢 up 8 from production) SEO: 95 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[claude]

Writing quality review

Overall this is a clear, well-structured addition. A few style guide issues to address:

Informal language

This isn't a problem for the other generated languages.

Contractions ("isn't") don't fit the professional, technical tone. Suggest:

This limitation does not affect other generated languages.

Missing comma after "e.g."

Two places use e.g. without the required comma:

• e.g. a type of ["string", "null"] → e.g., a type of ["string", "null"]
• Table cell: Non-null unions e.g. ["string", "integer"] → Non-null unions e.g., ["string", "integer"]

Heading voice

Per the style guide, headings should prefer imperative voice ("Configure the tracker", not "Tracker configuration"). Consider:

### Event specification names in Golang → ### Avoid name collisions in Golang

Bold removed from "does not work"

Removing **does not work** is correct — the style guide reserves bold for UI elements only. Good catch.