Format repository with purs-tidy #296
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
purs-tidy v0.9.1, config checked in
andys8
force-pushed
the
improvement/format-purs-tidy
branch
from
65e07ca
to
507061b
Compare
22 tasks
JordanMartinez
approved these changes
Aug 12, 2022
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With the goal of consistent formatting and import order across examples the repository is formatted with
purs-tidy, a dependency and the configuration are added to the repository. Asked upfront if a change like this makes sense and am open to apply changes to.tidyrc.jsonif they're prefered.Changes
make format)make formatCheckcommand is added and executed on CI