Adding features to control if the macro uses `env_logger` or `tracing` and allow more flexibility around logging initialization/configuration#11

Merged

JeremieRodon merged 15 commits intomasterfrom

Jan 9, 2026

Commits on Dec 14, 2025

First release candidate to provide the possibility of using tracing instead of log/env_logger as the log layer
JeremieRodon
committed

Commits on Dec 16, 2025

Fix: Both feature can be enabled at the same time, but I still have to make sure only one initialization code runs to avoid a panic
JeremieRodon
committed
Feat: Creating an independant feature flag for 'log' and making it enabled for both env_logger and tracing feature. This feature flag controls weither or not the generated code uses log::info!(...)…
JeremieRodon
committed
Feat: Added and documented an optional 'event_logging' parameter to the macro to control weither or not the Lambda event is dumped in the log or not (default to true)
JeremieRodon
committed
Fix: Typo in variable name
JeremieRodon
committed
Merge branch 'master' into feat-tracing
JeremieRodon
authored
Adding a compilation test using the new event_logging flag
JeremieRodon
committed

Commits on Jan 7, 2026