chore(docs): fix typo in table docs #4820
Merged
Conversation
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
There was a typo in the `sortCompare` key for the table components meta data inside `package.json`, which is fixed with this commit.
Codecov Report
@@ Coverage Diff @@
## dev #4820 +/- ##
=======================================
Coverage 99.93% 99.93%
=======================================
Files 263 263
Lines 5857 5857
Branches 1528 1528
=======================================
Hits 5853 5853
Misses 3 3
Partials 1 1Continue to review full report at Codecov.
|
tmorehouse
approved these changes
Feb 24, 2020
|
Thanks! |
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.
There was a typo in the
sortComparekey for the table components meta data insidepackage.json, which is fixed with this commit.Describe the PR
Simple typo fix in the table docs
PR checklist
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
The PR fulfills these requirements:
devbranch, not themasterbranch[...] (fixes #xxx[,#xxx]), where "xxx" is the issue number)fix(alert): not alerting during SSR render,docs(badge): update pill examples,chore(docs): fix typo in README, etc).