Mirror/zeek
1
0
Fork 0
mirror of https://github.com/zeek/zeek.git synced 2025-10-12 11:38:20 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

scripts: Use tpe instead of type_, again

Browse source 
The .rst generation doesn't escape the trailing `_` and the docs build
gets upset due to using `type` as a reference target then.

For the better or worse, revert to using tpe. Though I acknowledge this
means we need to be careful with trailing underscores because our docs
build is so fragile.

Partly reverts b9eabbabba.
This commit is contained in:
Arne Welzel 2025-07-03 20:25:10 +02:00
parent 388cbcee48
commit df581c59b4
7 changed files with 18 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

6
scripts/base/frameworks/intel/input.zeek
View file

@ -27,11 +27,11 @@ export {
##
## desc: The :zeek:type:`Input::EventDescription` record which generated the event.
##
## type_: The type of input event.
## tpe: The type of input event.
##
## item: The intel item being read (of type :zeek:type:`Intel::Item`).
##
global read_entry: event(desc: Input::EventDescription, type_: Input::Event, item: Intel::Item);
global read_entry: event(desc: Input::EventDescription, tpe: Input::Event, item: Intel::Item);
## This event is raised each time the input framework detects an error
## while reading the intel file. It can be used to implement further checks
@ -46,7 +46,7 @@ export {
global read_error: event(desc: Input::EventDescription, message: string, level: Reporter::Level);
}
event Intel::read_entry(desc: Input::EventDescription, type_: Input::Event, item: Intel::Item)
event Intel::read_entry(desc: Input::EventDescription, tpe: Input::Event, item: Intel::Item)
{
Intel::insert(item);
}