fix: correct displayName type in Sneak Peek AsyncAPI example - #5663
fix: correct displayName type in Sneak Peek AsyncAPI example#5663swarupasaroogumma wants to merge 1 commit into
Conversation
✅ Deploy Preview for asyncapi-website ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe rendered AsyncAPI example now represents the ChangesAsyncAPI Example Correction
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-5663--asyncapi-website.netlify.app/ |



Description
This PR updates the
displayNamefield type in the AsyncAPI document shown in the Sneak Peek example.Before:
After:
The AsyncAPI document example represents
displayNameas anobject, while the generated TypeScript and documentation preview both represent it as astring. This change makes the three previews consistent.Type of change
Testing
Summary by CodeRabbit
displayNamepayload property is displayed as a string.