From 8210b67325a3e49c36af8874d8c8fd53a3e572f0 Mon Sep 17 00:00:00 2001 From: Grzegorz Nosek Date: Tue, 9 Apr 2024 14:16:23 +0200 Subject: [PATCH] fix(doc): fix broken doc links --- falco_plugin/src/lib.rs | 2 +- falco_plugin/src/plugin/extract/mod.rs | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/falco_plugin/src/lib.rs b/falco_plugin/src/lib.rs index 919231b1..ddb0cca4 100644 --- a/falco_plugin/src/lib.rs +++ b/falco_plugin/src/lib.rs @@ -206,7 +206,7 @@ pub mod base { pub mod extract { /// # An event from which additional data may be extracted /// - /// The one notable thing about it is that it implements the [`EventInput`](`crate::EventInput`) + /// The one notable thing about it is that it implements the [`EventInputExt`](`crate::EventInputExt`) /// trait. You probably won't need to access any of its fields directly. pub use falco_plugin_api::ss_plugin_event_input as EventInput; pub use falco_plugin_api::ss_plugin_field_extract_input as FieldExtractInput; diff --git a/falco_plugin/src/plugin/extract/mod.rs b/falco_plugin/src/plugin/extract/mod.rs index f5ad3214..8d61f24b 100644 --- a/falco_plugin/src/plugin/extract/mod.rs +++ b/falco_plugin/src/plugin/extract/mod.rs @@ -154,7 +154,7 @@ where /// /// `arg` is the actual argument passed along with the field (see [`ExtractFieldRequestArg`]) /// - /// `event` is the event being processed (see [`EventInput`](`crate::EventInput`)) + /// `event` is the event being processed (see [`EventInputExt`](`crate::EventInputExt`)) /// /// `tables` is an interface to access tables exposed from Falco core and other plugins (see /// [`tables`](`crate::tables`))