Multiple `.after`'s only run the last hook

[jparris]

Problem

Modifying the readme example to have multiple afters will only run the last after.

Example afters

    World::cucumber()
        .init_tracing()
        .after(|_, _, _, _, _| async { tracing::info!("After 1") }.boxed_local())
        .after(|_, _, _, _, _| async { tracing::info!("After 2") }.boxed_local())
        .run("readme.feature").await;

Example output

Feature: Eating too much cucumbers may not be good for you
  Scenario: Eating a few isn't a problem
   ✔  Given Alice is hungry
   ✔  When she eats 3 cucumbers
   ✔  Then she is full
2025-04-01T22:26:48.283264Z  INFO scenario:after hook: double_after: After 2
[Summary]
1 feature
1 scenario (1 passed)
3 steps (3 passed)

Possible Solutions

• Add a warning that multiple afters have been set and only the last one will be run.
• Add support for multiple afters.

[tyranron]

@jparris yup, it wasn't intended to set multiple callbacks. We can call it multiple time to be able to overwrite the one set before. I think additional warning in the documentation and Book would be a good solution as for now. Adding ability to set multiple different hooks needs a thoughtful design, and I'd like no to hurry with such feature, as the demand for it is not high enough.

[tyranron]

Would love to see a PR, anyway.

[jparris]

Would love to see a PR, anyway.

Thanks. I've opened a PR feel free to tweak my wording.