Skip to content

Run prettier #7172

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

Merged
merged 1 commit into from
Feb 12, 2021
Merged

Run prettier #7172

merged 1 commit into from
Feb 12, 2021

Conversation

dblythy
Copy link
Member

@dblythy dblythy commented Feb 9, 2021

New Pull Request Checklist

Issue Description

Runs prettier on Parse Server (there are a few affected files)

@dblythy
Copy link
Member Author

dblythy commented Feb 9, 2021

Also, there are a couple of files which are changed using npm run prettier but changed back using npm run lint-fix. Which should be the priority?

@codecov
Copy link

codecov bot commented Feb 9, 2021

Codecov Report

Merging #7172 (67194ba) into master (e3ed6e4) will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #7172   +/-   ##
=======================================
  Coverage   93.91%   93.91%           
=======================================
  Files         169      169           
  Lines       12547    12547           
=======================================
  Hits        11784    11784           
  Misses        763      763           
Impacted Files Coverage Δ
src/Controllers/LiveQueryController.js 96.42% <100.00%> (-0.13%) ⬇️
src/Controllers/UserController.js 95.27% <100.00%> (ø)
src/RestQuery.js 95.53% <100.00%> (+<0.01%) ⬆️
src/Routers/FilesRouter.js 88.28% <100.00%> (ø)
src/Adapters/Files/GridFSBucketAdapter.js 79.50% <0.00%> (-0.82%) ⬇️
src/RestWrite.js 93.84% <0.00%> (+0.16%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e3ed6e4...6eba387. Read the comment docs.

@davimacedo
Copy link
Member

I think we should choose and rely in one of them. @dplewis @mtrezza thoughts?

@mtrezza
Copy link
Member

mtrezza commented Feb 9, 2021

There are things that lint doesn't do, but prettier does and vice versa. Not, because one is better than the other but because each has a slightly different although similar purpose. In short, one is focused on code quality, the other on code style.

I think we should decide the order in which they run - which will lead to different results - without expecting both to yield the same output.

I suggest the order to be prettier -> lint, because while code style is somewhat idiosyncratic, code quality seems to be less so.

@dblythy
Copy link
Member Author

dblythy commented Feb 10, 2021

Okay, cool. Good to know the process for the future. That's what I expected.

This PR is still the result of running:

npm run prettier
then
npm run lint-fix

On the master branch

@mtrezza
Copy link
Member

mtrezza commented Feb 10, 2021

I think that makes sense. @davimacedo ?

@davimacedo
Copy link
Member

Yes. That makes sense. I believe it is actually already automated here, right?

@dblythy
Copy link
Member Author

dblythy commented Feb 12, 2021

I think it only affects files that are edited though. If you run prettier on the master and then lint-fix, the result is this PR

Copy link
Member

@mtrezza mtrezza left a comment

Choose a reason for hiding this comment

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

LGTM!

@mtrezza mtrezza merged commit e53b6c2 into parse-community:master Feb 12, 2021
@dblythy dblythy deleted the prettier branch February 12, 2021 16:55
dplewis pushed a commit that referenced this pull request Feb 21, 2021
@dblythy dblythy mentioned this pull request Mar 18, 2021
2 tasks
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 5.0.0-beta.1

@parseplatformorg parseplatformorg added the state:released-beta Released as beta version label Nov 1, 2021
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 5.0.0

@parseplatformorg parseplatformorg added the state:released Released as stable version label Mar 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:released Released as stable version state:released-beta Released as beta version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants