-
Notifications
You must be signed in to change notification settings - Fork 17
Add getting started React #436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report
@@ Coverage Diff @@
## 6-dev #436 +/- ##
=======================================
Coverage 96.15% 96.15%
=======================================
Files 33 33
Lines 1612 1612
=======================================
Hits 1550 1550
Misses 62 62 Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #436 +/- ##
=======================================
Coverage 96.03% 96.03%
=======================================
Files 33 33
Lines 1641 1641
=======================================
Hits 1576 1576
Misses 65 65 Continue to review full report at Codecov.
|
Why is there a |
The |
This PR should be on the |
And I think you should do as for your Vue.js getting started: having a submenu with this "React Redux" getting started so in the futur we can have another one with only "React" |
Co-Authored-By: Adrien Maret <amaret93@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Provided cypress tests are fixed
Travis deadlinks fails are fixed in this PR |
Cypress tests are still failing. |
## What does this PR do? Add Kuzzle React getting-started. This getting-started have been merge in the last doc [#291](kuzzleio/documentation#291) The last getting started app was builted progressively and some code was rewrite during the reading. I had to rewrite lot of parts to remove that because it implicated some untested lines. I avoid hard snippets written in the readme too. I removed the tested snippets and add cypress to test the app globally. The app use the current 6-dev sdk version with the ugly post-install line in `doc/6/getting-started/.react/package.json` ### How should this be manually tested? - Step 0 : Kuzzle running stack - Step 1 : cd doc/6/getting-started/.react - Step 2 : yarn install - Step 3 : yarn start & (if error add `SKIP_PREFLIGHT_CHECK=true`) - Step 4 : npm run test ### Other changes / ### Boyscout /
# Description Import #431 and #436 to v7: commits were cherry-picked, then the getting started directories were moved to the `doc/7` documentation directory. Finally, the `test-doc` script has been adapted to run tests on the v7 version of the getting started. Those are the only changes made, there should be no need to review the full content of this PR (but you may do it if you want to)
What does this PR do?
Add Kuzzle React getting-started.
This getting-started have been merge in the last doc #291
The last getting started app was builted progressively and some code was rewrite during the reading.
I had to rewrite lot of parts to remove that because it implicated some untested lines. I avoid hard snippets written in the readme too.
I removed the tested snippets and add cypress to test the app globally.
The app use the current 6-dev sdk version with the ugly post-install line in
doc/6/getting-started/.react/package.json
How should this be manually tested?
SKIP_PREFLIGHT_CHECK=true
)Other changes
/
Boyscout
/