Skip to content

ci: Fix eslint config #9723

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

Open
wants to merge 2 commits into
base: alpha
Choose a base branch
from
Open

Conversation

dplewis
Copy link
Member

@dplewis dplewis commented Apr 17, 2025

Pull Request

Issue

Eslint is broken, runs prettier

Copy link

🚀 Thanks for opening this pull request!

Copy link

codecov bot commented Apr 17, 2025

Codecov Report

Attention: Patch coverage is 90.90909% with 9 lines in your changes missing coverage. Please review.

Project coverage is 92.98%. Comparing base (9a2cffe) to head (3edda90).

Files with missing lines Patch % Lines
src/SchemaMigrations/DefinedSchemas.js 55.55% 4 Missing ⚠️
src/Auth.js 75.00% 1 Missing ⚠️
src/Config.js 83.33% 1 Missing ⚠️
src/Controllers/SchemaController.js 90.00% 1 Missing ⚠️
src/Routers/GraphQLRouter.js 0.00% 1 Missing ⚠️
src/middlewares.js 91.66% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##            alpha    #9723      +/-   ##
==========================================
- Coverage   93.01%   92.98%   -0.04%     
==========================================
  Files         187      187              
  Lines       15081    15112      +31     
  Branches      174      174              
==========================================
+ Hits        14028    14052      +24     
- Misses       1041     1048       +7     
  Partials       12       12              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@dplewis dplewis requested a review from a team April 17, 2025 16:49
Comment on lines +334 to +336
it_id('23caddd7-bfea-4869-8bd4-0f2cd283c8bd')(it)(
'can start Parse Server with auth via CLI',
done => {
Copy link
Member

Choose a reason for hiding this comment

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

What line length is this enforcing? Looks less readable to me this way.

Copy link
Member Author

Choose a reason for hiding this comment

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

Looks like prettier has a 100 line length

Copy link
Member

Choose a reason for hiding this comment

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

Should we set this to longer lines, like 170?

Copy link
Member Author

Choose a reason for hiding this comment

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

We could but it’s up to you to review 170+ files being changed. My plan was to remove prettier and husky anyway like the JS SDK. Should I just redo this PR without running prettier?

Copy link
Member

@mtrezza mtrezza Apr 23, 2025

Choose a reason for hiding this comment

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

Should I just redo this PR without running prettier?

I think that would be good; we may consider running a reformat across all files in a dedicated PR, if it's worth it. It's just such a large change that I'm afraid it would create merge conflicts or complicated rebases across pending PRs. Maybe we can do this if we get to a point where we clean up the PR list.

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.

2 participants