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

make rules scala compatible with bazelbsp #57

Closed
wants to merge 1 commit into from

Conversation

ryan28561
Copy link

@jadenPete actually wrote all of this, it just adds compiler information to the bazel providers(? or something, I don't know bazel that well) so bazelbsp can use it.

use_ijar = ctx.attr.use_ijar,
version = ctx.attr.version,
)
return struct(

Choose a reason for hiding this comment

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

This is a step backwards. Why are we doing this?

Old implementation functions can also be written in a legacy style where the implementation function returns a struct instead of list of provider objects. This style is strongly discouraged and rules should be migrated away from it.

https://bazel.build/extending/rules#providers

Copy link
Author

Choose a reason for hiding this comment

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

Huh, so I don't want to speak for Jaden, who actually knows what he's doing, but I seem to recall him saying that we needed it so we could get access to it from the aspect in bazel-bsp/hirschgarten. I did just update it to use ["_ScalaConfiguration"] instead of .scala_configuration though, and afaict, it seems to work exactly the same.

Copy link
Author

Choose a reason for hiding this comment

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

Ah ok, I think I fixed it so we won't need this. JetBrains/hirschgarten@7077bff

@ryan28561 ryan28561 closed this Oct 7, 2024
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.

4 participants