Add dev script to skip linting and create-react-play when starting to… #1400
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.
Description
Adding a dev script command in package.json to skip create-react-play each time we start the application.
We don't load the linting of files too as they are done now automatically with Husky, so we don't have problem with non linted files.
On linux system, often permission are change without the user intervention and when we are not use to linux, we didn't know how to handle the problem and lost time to figure out how to bypass it.
I've done at least more than 10 branches creation to test if i can push only my 2 files ( as currently in this branch ) instead of all the files in the project because the permission was changed on them and git pushed them too.
Fixes #1399
Type of change
add "dev" script in package.json
add .gitconfig to ignore file permission change in the system.
Please delete options that are not relevant.
How Has This Been Tested?
1./ dev script
By using the command and see if the application is ok.
Start must be done at least one time, because create-react-play need to be run to create the index.js file in the plays folder.
2./ .gitconfig
By pushing the change online, and see if only the 2 modified files are committed and not all the files in the project.
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
No specific test except running the program as usually.
Checklist:
Screenshots or example output