docs(expo): use emoji in feature support tables - #2013
Merged
dinwwwh merged 3 commits intoSep 12, 2026
Conversation
Replace the Yes/No and Works/Fails cells in the Expo adapter's feature support tables with ✅ and ❌ and align the table columns, matching the style used by the rate limit adapters table.
More templates
@orpc/ai-sdk
@orpc/arktype
@orpc/bun
@orpc/client
@orpc/cloudflare
@orpc/contract
@orpc/experimental-effect
@orpc/evlog
@orpc/hibernation
@orpc/json-schema
@orpc/experimental-msw
@orpc/nest
@orpc/next
@orpc/node
@orpc/openapi
@orpc/opentelemetry
@orpc/pinia-colada
@orpc/pino
@orpc/publisher
@orpc/ratelimit
@orpc/server
@orpc/shared
@orpc/swr
@orpc/tanstack-query
@orpc/trpc
@orpc/valibot
@orpc/zod
commit: |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Contributor
Contributor
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
- Feature Support table —
Yes/Nocells inapps/content/docs/adapters/expo.mdxreplaced with ✅/❌, whileBufferedcells remain text because they describe partial support. - Nested binary table —
Works with the Blob polyfillbecomes✅ with the Blob polyfill, and bothFailscells become ❌. - Column alignment — both tables are padded so the pipes line up.
Every emoji maps 1:1 to the previous Yes/No/Fails value, so the support matrix says exactly what it said before; this is a pure presentation change with no code or build surface.
openrouter/deepseek/deepseek-v4.1-flash (free via Pullfrog for OSS) | 𝕏
Collapse the feature support table to Fetch and WebSocket columns and mark cells that only work when buffered or with the Blob polyfill as 🟡 with the condition inline.
Restore the two notes on buffered fetch uploads and nested binary over WebSocket, and tie them to the 🟡 cells in the table.
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.

The Expo adapter page now marks feature support with ✅, 🟡, and ❌ instead of Yes/No and Works/Fails. The two "+ polyfill" columns are folded into the plain Fetch and WebSocket columns, so the table is half as wide and each cell states its own condition.
Changes
Testing