-
Notifications
You must be signed in to change notification settings - Fork 1
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
Refactor(Linting): ESLint, Prettier for Acceptance Tests #140
Refactor(Linting): ESLint, Prettier for Acceptance Tests #140
Conversation
In the package.json at the root of the directory, please modify the check:all script to have the lint:all instead of the lint:client. |
Looks like eslint was not properly installed in the acceptance directory. Install eslint and prettier into the acceptance directory so that the GitHub Action "test-pipeline.yaml" passes properly. |
The repository root package.json install:all command is missing a command to install dependencies in the acceptance folder. Please write a command for installing acceptance dependencies and attach it to the install:all command. |
Add the install:acceptance command to the install:all command in the root package.json. Use the && annotation for appending it to the end of the install:all command. |
Remove the install:acceptance command from the root package.json, also remove it from the install:all command within the same package.json. The GitHub test-pipeline action is still failing, saying eslint cannot be found when the lint:acceptance command is executed. Resolve this issue as well. |
`npm run check:all
sh: 1: eslint: not found Fix the above error that was identified from the GitHub Action, test-pipeline.yaml |
Modify the .prettierrc.json and .eslintec.json in the acceptance directory to match the client directory's .prettierrc.json and .eslintec.json. Ensure that the GitHub Actions under test-pipeline.yaml pass. There is an error with the npm run lint:all command, and more specifically the lint:acceptance command and execution. |
GitHub actions yielded the following error. The relevant lines from the logs corresponding to the error are:
The command that failed is There are a lot of errors. This is likely a larger issue with the PR and not a small linting/type-checking issue. This is likely a linting or type-checking issue with the source code but if you are updating the GitHub Actions or versioning, this could be an issue with the GitHub Action yaml files. |
GitHub actions yielded the following error. The relevant lines from the logs corresponding to the error are:
The command that failed is There are a lot of errors. This is likely a larger issue with the PR and not a small linting/type-checking issue. This is likely a linting or type-checking issue with the source code but if you are updating the GitHub Actions or versioning, this could be an issue with the GitHub Action yaml files. |
GitHub actions yielded the following error. The relevant lines from the logs corresponding to the error are:
The command that failed is There are a lot of errors. This is likely a larger issue with the PR and not a small linting/type-checking issue. This is likely a linting or type-checking issue with the source code but if you are updating the GitHub Actions or versioning, this could be an issue with the GitHub Action yaml files. |
Description
This PR adds ESLint and Prettier to the
acceptance
subproject and updates the rootpackage.json
to include linting and formatting commands for theacceptance
subproject. This ensures consistency in linting and formatting rules across theclient
andacceptance
subprojects.Summary of Changes
acceptance
subproject, pointing to the existing configuration files in theclient
subproject.package.json
to include linting and formatting commands for theacceptance
subproject.package.json
for linting theacceptance
subproject and linting both theclient
andacceptance
subprojects.Please review and merge this PR to enable linting and formatting in the
acceptance
subproject.Fixes #110.
To checkout this PR branch, run the following command in your terminal: