Skip to content
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

Fix/270 fix eslint config #271

Merged
merged 13 commits into from
Sep 13, 2023
Merged

Fix/270 fix eslint config #271

merged 13 commits into from
Sep 13, 2023

Conversation

April-Bates-Dev
Copy link
Collaborator

  • Editing CI to include linting
  • Fixing linting errors
  • Fixing broken linting config

@April-Bates-Dev April-Bates-Dev force-pushed the fix/270-fix-eslint-config branch 2 times, most recently from e3c80c9 to b245340 Compare September 12, 2023 11:58
@github-actions
Copy link
Contributor

github-actions bot commented Sep 12, 2023

Test results summary:

✅ [PASS] - Test case: Bad variable name
❌ [FAIL] - Test case: Exposed secret
✅ [PASS] - Test case: Too many nested loops
⚠️ [WARN] - Test case: Unawaited Promise

SUMMARY: ✅ PASS: 2 - ⚠️ WARN: 1 - ❌ FAIL: 1


Tests Powered by Code Review GPT

@April-Bates-Dev April-Bates-Dev force-pushed the fix/270-fix-eslint-config branch 3 times, most recently from 32f3040 to 8058038 Compare September 12, 2023 13:07
@April-Bates-Dev April-Bates-Dev force-pushed the fix/270-fix-eslint-config branch 5 times, most recently from 389d864 to 9492b00 Compare September 12, 2023 13:42
@@ -39,8 +39,6 @@ const formatTestResult = (result: testResult, message: string): string => {
return chalk.yellow(`⚠️ [WARN] - ${message}`);
case testResult.FAIL:
return chalk.red(`❌ [FAIL] - ${message}`);
default:
throw new Error(`Unknown test result: ${result}`);
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[Note] Removed because it's an impossible case- there are only 3 options within the enum- other options are impossible and it threw a linting error

@April-Bates-Dev April-Bates-Dev force-pushed the fix/270-fix-eslint-config branch 2 times, most recently from ad0a2e2 to 4e64014 Compare September 13, 2023 10:05
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we have a master file and then each sub file inherits from it.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think if we were gonna have a shared file like that we are gonna have monorepo issues 🤔

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I personally am in favour of fixing this when we have the monorepo setup

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can add it to the monorepo ticket

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure I see the point in changing this to make it much more complicated if it still doesnt work? I think I would prefer if it failed

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm- I see what you are saying, but it if is reverted we have undone one fix (the folders issue). I think it is better to leave it in a state that we know is closer to working so someone doesn't end up solving the same problem again.

@April-Bates-Dev April-Bates-Dev merged commit 0309c70 into main Sep 13, 2023
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants