Docs/fix all custom components documentation #2014
Merged
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
jquense
approved these changes
Aug 27, 2021
|
thanks! |
Most welcome! |
|
Could you make an example for the the custom components? |
|
🎉 This PR is included in version 0.36.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Me and my colleagues had a hard time figuring out what was possible with the library. I dove into the source code and realised that there was a bunch of documentation, but it was not rendering.
The docs that I moved from the top of the
Calendar.jsfile: I don't know if these pieces of information are still relevant, but I added them to the intro. They were not rendering at all before.I also added a comma so the custom component docs would render properly, and I added more info on the messages.
Might help solve:
Before:
After: