-
Notifications
You must be signed in to change notification settings - Fork 81
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
Drop Scala 2.11 support and update pprint/fnase/metaconfig #603
Conversation
0cacac6
to
cddeacd
Compare
scalameta/metaconfig#151 is required to make this work. |
cddeacd
to
3ca07be
Compare
77e7717
to
5208716
Compare
Fine by me👍 |
…tically by steward
5208716
to
d8d4f97
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This has a bulk of changes that put me off metaconfig upgrade in https://github.com/scalameta/mdoc/pull/563/files
I should rebase my PR at some point.
I just ran into a |
I am working on that, but the pprint icompatibility is proving to cause a whole lot more problems than expected 😓 |
@mrdziuban This should work with the latest release, do try it out 🙏 |
Confirmed, mdoc 2.3.0 and pprint 0.7.1 play nicely together in my codebase -- thank you! |
Fixes #602
It seem there were a lot of changes in pprint:
com-lihaoyi/PPrint@7fead8d#diff-492a668d78a78a50945e22826d563419a9c827b6164bca4bfedb3a7c4f66d551
It seems we need t first bump this in metaconfig.it's updated, but metaconfig no longer publishes for 2.11, so we need to drop it in mdoc also, which I think is not an issue, since people can stay with older versions for now. Opinions?