-
Notifications
You must be signed in to change notification settings - Fork 1
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
fix(build/builtin): properly auto-detect modules #238
base: master
Are you sure you want to change the base?
Conversation
Actually, this was just a bug in I've also moved the |
|
70a1be4
to
d8f8ee0
Compare
6319d9a
to
90c886b
Compare
37bc52a
to
0a91129
Compare
0a91129
to
83304bf
Compare
83304bf
to
6f36aad
Compare
6f36aad
to
8c83bc8
Compare
daec215
to
b521dcb
Compare
b521dcb
to
5b3b7b7
Compare
5b3b7b7
to
13b5367
Compare
Turns out we should only auto detect modules if no modules are specified (for example, successfully auto detecting modules breaks |
13b5367
to
e832971
Compare
.into_iter() | ||
.chain(self.modules) | ||
.collect::<HashMap<_, _>>(); | ||
let modules = if self.modules.is_empty() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question(non-blocking): is this luarocks's behaviour too? Is there no situation where a few modules are defined by the rockspec author and they "expect" the rest to be autodetected? Given the amount of wacky code we've seen it might be worth checking haha
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure.
I tried installing luassert
and it failed if using both the rockspec modules and the auto-detected modules.
But perhaps instead we should just filter out files in the rockspec modules when auto-detecting modules.
@@ -49,6 +49,7 @@ thiserror = "2.0.0" | |||
gpgme = "0.11.0" | |||
futures = "0.3.31" | |||
async-recursion = "1.1.1" | |||
predicates = "3.1.2" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
issue: I only see this used in tests. Should this be part of dev-dependencies
instead?
Fixes #236.