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

improvement: Regenerate Bazel files if any are missing #6143

Merged
merged 1 commit into from Feb 20, 2024

Conversation

tgodzik
Copy link
Contributor

@tgodzik tgodzik commented Feb 20, 2024

Partly fixes #6131

It seems that Bazel BSP creates empty projectview if it doesn't exist.

Partly fixes scalameta#6131

It seems that Bazel BSP creates empty projectview if it doesn't exist.
Copy link
Member

@jkciesluk jkciesluk left a comment

Choose a reason for hiding this comment

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

This help, but I don't think it solves the problem - if we remove projectview, then save a file, empty projectview gets created during compilation

@tgodzik
Copy link
Contributor Author

tgodzik commented Feb 20, 2024

This help, but I don't think it solves the problem - if we remove projectview, then save a file, empty projectview gets created during compilation

I know, but we need to fix this anyway here and in Bazel BSP

@tgodzik tgodzik merged commit c7759e1 into scalameta:main Feb 20, 2024
25 of 26 checks passed
@tgodzik tgodzik deleted the recreate branch February 20, 2024 16:53
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.

Bazel: failing build import when projectview.bazelproject is missing
2 participants