You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 3, 2022. It is now read-only.
In the Javascript ecosystem, Prettier has quickly become the dominant code formatter, for a variety of reasons including execution speed, GitHub stars, tool integration, and simplicity. In fact, @actions/toolkit, @actions/setup-node, @actions/typescript-action, @actions/labeler, @actions/cache, and @actions/checkout are all already using Prettier. For consistency, this project should, as well.
I've already made a pull request for this work: #16.
The text was updated successfully, but these errors were encountered:
Fixed with #20 and #23 - thanks for pointing this out. Brings this inline with the other repos like toolkit with the same rules and approach used there.
Using an automated formatted for code is a good idea, for several reasons:
See https://prettier.io/docs/en/why-prettier.html for more detail on these points.
In the Javascript ecosystem, Prettier has quickly become the dominant code formatter, for a variety of reasons including execution speed, GitHub stars, tool integration, and simplicity. In fact,
@actions/toolkit
,@actions/setup-node
,@actions/typescript-action
,@actions/labeler
,@actions/cache
, and@actions/checkout
are all already using Prettier. For consistency, this project should, as well.I've already made a pull request for this work: #16.
The text was updated successfully, but these errors were encountered: