Skip to content

Conversation

@evantypanski
Copy link
Contributor

The name of the analyzer was used for hooks, but this doesn't work if there are multiple modules and they have hooks. One hooks file is made for each module, so they should all be included.

For context, I encountered this with the Redis analyzer. The analyzer is named Redis, but hooks are in the RESP module, so it gave linker errors when building.

@evantypanski evantypanski requested a review from rsmmr March 17, 2025 20:33
The name of the analyzer was used for hooks, but this doesn't work if
there are multiple modules and they have hooks. Or, if the name differs
from the module which contains hooks.
@evantypanski evantypanski force-pushed the topic/etyp/spicy-plugin-hooks-fix branch from 8f06197 to c20e282 Compare March 17, 2025 20:39
@ckreibich
Copy link
Member

Evan if a module is spread across multiple .spicy files (not a common thing to do, but I don't think Spicy prohibits it), does this work correctly? I.e., does this kick in on the resulting overall contents of a module, or per-file? I think it's the former, but figured I'd ask.

@rsmmr
Copy link
Member

rsmmr commented Mar 18, 2025

Evan if a module is spread across multiple .spicy files (not a common thing to do, but I don't think Spicy prohibits it)

Actually it does not allow that: one file per module only.

@evantypanski
Copy link
Contributor Author

@evantypanski evantypanski merged commit 1865120 into master Mar 18, 2025
1 check passed
@evantypanski evantypanski deleted the topic/etyp/spicy-plugin-hooks-fix branch March 18, 2025 13:32
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