docs: 📝 add explicitly call to HybridObject constructor #366
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Good point! I'm trying to keep the docs very simple and easy to read, and I think with this change there is now a layout shift when switching between languages... 😅 |
|
Do you see a layout shift because now we have different card height for each language? |
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.
Hi, it seems like that from version 0.6.0 it's required to call
HybridObjectconstructor since it's virtual, this PR add this suggestions inside the docs.Maybe would be also helpful to specify it somewhere in the doc so we can avoid this error at runtime, if someone have any suggestion I can it ofc: