-
Notifications
You must be signed in to change notification settings - Fork 78
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
Fantomas5 #194
Fantomas5 #194
Conversation
My mother always told me, "if you don't have anything nice to say, don't say anything at all." So I'll abstain, and leave the decisions to folks who have more skin in the game. 👍 |
I've always liked automated formatting. But it's been such a long time since I've contributed to this repository that I don't feel my voice has much value 😉 |
I love the idea! Can we somehow help with the initiative? |
I think that I do not need technical help, PR is already green. I'll wait for the next patch release for Fantomas to update it and format ignored files. But I need help with the review of the change. Currently, I used my |
@sergey-tihon is this ready for review? |
@gdziadkiewicz yes, but after merging this we break all other PRs |
@sergey-tihon @gdziadkiewicz You should proceed with this - other PRs can be fixed up by
|
BTW looking through the code in this repo reminds me what an excellent set of F# samples it is |
@sergey-tihon could you refresh this branch with master and resolve those two small conflicts? |
* commit '12972997d3782c58f81404593deb27e4e975e2e6': RoseTree. Fix a broken link in the comments. * Adds mapi variant and tests # Conflicts: # src/FSharpx.Collections/PersistentVector.fs # tests/FSharpx.Collections.Tests/PersistentVectorTest.fs
fa51d3c
to
83fdd98
Compare
@gdziadkiewicz done |
This draft is here to check with maintainers and core contributors Fantomas 5 formatting and decide merge or don't
Detected issues:
Would love to hear opinions/reactions from @forki @jackfoxy @pblasucci @eacasanovaspedre @gdziadkiewicz @sideeffffect @gsvgit