Skip to content
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

Updated sbt plugin version on the website #1494

Merged
merged 1 commit into from
Sep 8, 2019
Merged

Updated sbt plugin version on the website #1494

merged 1 commit into from
Sep 8, 2019

Conversation

poslegm
Copy link
Collaborator

@poslegm poslegm commented Sep 2, 2019

No description provided.

Copy link
Member

@tanishiking tanishiking left a comment

Choose a reason for hiding this comment

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

Thanks!
Maybe we can write something like "x.x.x" here instead of a specific version (like "2.0.4") so that we don't need to update here for every release of sbt-scalafmt because we can see the latest version of sbt-scalafmt through the maven badge below.

@tanishiking tanishiking merged commit 34253e8 into scalameta:master Sep 8, 2019
@poslegm poslegm deleted the patch-2 branch September 8, 2019 14:09
@poslegm
Copy link
Collaborator Author

poslegm commented Sep 9, 2019

I don't like "x.x.x" in documentation because I can't simply copy-paste it into my build.sbt 😄

@tanishiking
Copy link
Member

It makes sense 👍 Hmm, I hope we can update this automatically somehow. 🤔

@ches
Copy link
Contributor

ches commented Oct 8, 2019

Hmm, I hope we can update this automatically somehow.

There is already the badge sbt-scalafmt Maven Central directly below the addSbtPlugin snippet on the doc site that shows the latest version of the sbt plugin from Maven Central. Perhaps it can be made more obvious, although it doesn't completely solve the copy-paste problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants