Document CLI and tutorial workflow
@StuffByLiang ya está trabajando en esto.
Desde el 21/12/2020.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Goals
One of the main goals this fall was to build a scaffold/basic structure for a react native tutorial project, and to plan out how the end user would go from start to finish while navigating through each tutorial step.
Approach Summary
Our approach was to use git to manage the tutorial steps.
The user would clone the tutorial repository, which is the default react-native application shell and would immediately work on step one. Once finished, their code would be ran against a set of test suites created for that tutorial step, and upon passing, the set of tests for the next tutorial step would automatically be added to the project and the user would continue to work on the next task.
Implementation Details
When do we run the test suite against their code?
-
We use Git Hooks to run custom commands when certain important actions occur. Specifically, we will use git 'pre-commit' and 'post-commit' hooks. We use Husky to help us implement these.
- pre-commit: this hook is run before the git commit runs through to 'inspect' the commit. You can run tests and if they fail, the git commit will also faill
- post-commit: this hook is run when the git commit succeeds and is completed.
-
This is what how we use husky: the following code is located in the package.json folder.

-
When the tutorial user thinks they have completed the tutorial step, they should perform a 'git commit'. we run npm test, and if that fails, then the commit message is rejected. If all tests pass, we run a post-commit hook that calls our cli and asks it to add the next set of tests to the current branch that the user is working on
Command Line Interface Implementation
Libraries used
- in progress
- Lenguaje dominante
- JavaScript
- Estrellas
- 6
- Forks
- 0
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de MLH-Fellowship/react-native-tutorial
-
Meeting notes Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 30/100
MLH-Fellowship/react-native-tutorial#39 · 1 comentario · 4 reacciones ·
-
MLH-Fellowship/react-native-tutorial#36 · 1 comentario · 1 asignado ·
-
MLH-Fellowship/react-native-tutorial#35 · 3 comentarios · 1 asignado ·
-
MLH-Fellowship/react-native-tutorial#34 · 1 asignado ·
-
Research Branching Model: CLI Abierto
MLH-Fellowship/react-native-tutorial#20 · 2 comentarios · 2 asignados ·
Todos los issues de MLH-Fellowship/react-native-tutorial
Issues similares
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
avniproject/avni-client#2135 ·
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
babalae/bettergi-scripts-list#3674 ·
-
A-Release-Notes C-Editing D-Modest S-Ready-For-Implementation
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
bevyengine/bevy-website#2595 ·
-
ecosystem wording
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
matrix-org/matrix.org#3649 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
vadimdemedes/ink#1029 ·