doc: Automatically test quickstart document for state API #446
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
`files` -> `file`
Codecov Report
@@ Coverage Diff @@
## main #446 +/- ##
=======================================
Coverage 60.50% 60.50%
=======================================
Files 118 118
Lines 6357 6357
=======================================
Hits 3846 3846
Misses 2142 2142
Partials 369 369 Continue to review full report at Codecov.
|
zhenjunMa
approved these changes
Apr 2, 2022
Xunzhuo
approved these changes
Apr 5, 2022
JervyShi
approved these changes
Apr 5, 2022
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.
What this PR does:
I think we can use some tool to test quickstart document for state API, automatically.
document on how to use it:
https://seeflood.github.io/layotto/#/zh/development/test-quickstart
Which issue(s) this PR fixes:
Fixes #447
Special notes for your reviewer:
Does this PR introduce a user-facing change?: