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

Allow not having a records directory #64

Merged
merged 2 commits into from
Sep 7, 2022

Conversation

brentleyjones
Copy link
Contributor

It's valid to not have records (i.e. an empty swift file), and Bazel won't create empty directories when downloading from a remote cache.

It's valid to not have records (i.e. an empty swift file), and Bazel won't create empty directories when downloading from a remote cache.

Signed-off-by: Brentley Jones <github@brentleyjones.com>
@brentleyjones brentleyjones force-pushed the bj/allow-not-having-a-records-directory branch from bb0fd99 to 987a428 Compare September 7, 2022 17:55
@brentleyjones brentleyjones enabled auto-merge (squash) September 7, 2022 17:55
@keith
Copy link
Member

keith commented Sep 7, 2022

hrm, i imagine more often than not this is an actual error?

@brentleyjones
Copy link
Contributor Author

I encountered this in the wild, especially with the global indexing feature in rules_swift. Do you want it behind a flag as well?

@keith
Copy link
Member

keith commented Sep 7, 2022

it has to be a module with no source files with content?

@brentleyjones
Copy link
Contributor Author

brentleyjones commented Sep 7, 2022

Yes. A couple people have encountered this. We need a way to allow this, either with a flag or warning (preferably with a flag).

index-import.cpp Outdated Show resolved Hide resolved
index-import.cpp Outdated Show resolved Hide resolved
Signed-off-by: Brentley Jones <github@brentleyjones.com>
@brentleyjones brentleyjones merged commit 46450da into main Sep 7, 2022
@brentleyjones brentleyjones deleted the bj/allow-not-having-a-records-directory branch September 7, 2022 18:12
@erikkerber
Copy link

Can definitely happen in large projects assuming you don't lint for these things 😅

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