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

Bloop: Fixed re-generation of bloop config dir #2164

Merged
merged 2 commits into from
Dec 5, 2022

Conversation

lefou
Copy link
Member

@lefou lefou commented Dec 3, 2022

The bloop.writeConfig was a cached target, but it generated files outside of T.dest. Instead, it should be a command.

To preserve source and binary compatibilty, I created a new command writeConfigFile, and let the writeConfig target forward the result of writeConfigFile.

The `bloop.writeConfig` was a cached target, but it generated files
outside `T.dest`. Instead, it should be a command.

To preserve source and binary compatibilty, I created a new command
`writeConfigFile` command, and let the `writeConfig` target forward
the result of `writeConfigFile`.
@lefou lefou changed the title Bloop: Fixed re-generated of bloop config dir Bloop: Fixed re-generation of bloop config dir Dec 3, 2022
@adpi2
Copy link
Contributor

adpi2 commented Dec 5, 2022

Thanks for taking care of that

Copy link
Contributor

@adpi2 adpi2 left a comment

Choose a reason for hiding this comment

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

LGTM

One question though: Would Mill remove old config files for modules that no longer exists?

@lefou
Copy link
Member Author

lefou commented Dec 5, 2022

LGTM

One question though: Would Mill remove old config files for modules that no longer exists?

Yes. It's simply deleting all other *.json files it finds in the bloop config dir.

@lefou lefou merged commit 895f175 into com-lihaoyi:main Dec 5, 2022
@lefou lefou deleted the fix-bloop branch December 5, 2022 13:13
@lefou lefou added this to the 0.10.10 milestone Dec 5, 2022
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.

2 participants