-
Notifications
You must be signed in to change notification settings - Fork 37
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
External hook implementation for fields/units and error messages #1465
Comments
Yes, it's meant to work. I think we ran into this issue before somewhere but looks like we don't track it in a ticket yet.
One clarification: |
Assuming `Foo::X` is a unit type, these two are now equivalent: on Foo::X::%done { } on Foo::X { } Addresses #1465.
Assuming `Foo::X` is a unit type, these two are now equivalent: on Foo::X::%done { } on Foo::X { } Addresses #1465.
Assuming `Foo::X` is a unit type, these two are now equivalent: on Foo::X::%done { } on Foo::X { } Addresses #1465.
* origin/topic/robin/gh-1465-implicit-done: Produce better error message when `%XXX` hook is used on a unit field. Support skipping explicit `%done` in external hooks.
@J-Gras found that the package template showed
on Module::Unit { ... }
usages in a comment and fixed it to explicitly use a::%done
as without that it's not functional: zeek/package-template@c429a20Two topics related to that:
Should implicit
%done
work for external hooks on units as previously shown in the template, or was that an oversight? For unit fields%done
is not needed, though that may be mixing different concepts that only on first sight seem related.The error messages produced for hooks that have an extra %done on unit fields or a a missing %done on units
fieldsare not helpful for diagnosing the issue.Test files:
The text was updated successfully, but these errors were encountered: