Skip to content

V11 - Message Emittence from direct source#1879

Open
luke-hill wants to merge 9 commits into
mainfrom
feature/v11_message_emittence_at_source
Open

V11 - Message Emittence from direct source#1879
luke-hill wants to merge 9 commits into
mainfrom
feature/v11_message_emittence_at_source

Conversation

@luke-hill
Copy link
Copy Markdown
Contributor

Description

This epic PR will move as many / all of the message emittence events to the direct source of truth. i.e. from where @configuration.notify is called.

Most of these should be easy to do, a few may require some additional bits of work

Type of change

Please delete options that are not relevant.

  • Refactoring (improvements to code design or tooling that don't change behaviour)

NB: A single Changelog message will be written here once all are done

Please add an entry to the relevant section of CHANGELOG.md as part of this pull request.

Checklist:

Your PR is ready for review once the following checklist is
complete. You can also add some checks if you want to.

  • Tests have been added for any changes to behaviour of the code
  • New and existing tests are passing locally and on CI
  • bundle exec rubocop reports no offenses
  • RDoc comments have been updated
  • CHANGELOG.md has been updated

luke-hill and others added 9 commits May 26, 2026 15:32
* Add envelope generation at source for gherkin_source_read event

* Do not double fire events
…kFinished (#1878)

* Add in logic for both run hook events to be passed as messages

* Store test_run_started_id cache on config class instance

* Pass in the test_run_started_id on hook_run_started message generation and remove faux update from envelope emittence
…_source' into feature/v11_message_emittence_at_source
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant