docs: fix incorrect claim about Schema component type discovery #3432
+2
−2
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.
Summary
Updates the Schema component documentation to correct an inaccurate claim about type discovery. The previous documentation stated that "types exclusively used by websockets or webhooks won't be available," but after investigating the fern-platform codebase, I found that the
IrGraph.build()method does include types from webhooks and websocket channels.The actual limitation is that types must be defined as named schemas in the OpenAPI spec (under
components/schemas) to be discoverable - inline schemas that aren't extracted as named types won't be available.Review & Testing Checklist for Human
IrGraph.build()in fern-platform), not empirically tested.<Schema type="SomeWebhookType" />with a type that's only referenced by a webhook to confirm it works.ACHDetailstype not being found. The new docs suggest this is because it might be an inline schema - verify this is the actual root cause.Notes
WebhookExamplesClient.tsx,generateWebhookExample.ts). If webhook examples aren't appearing for Square, it may be a separate issue with their specific OpenAPI spec.