Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update DSL hook processing logic to be consistent #3376

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

joshuay03
Copy link
Contributor

@joshuay03 joshuay03 commented May 2, 2024

Description

Noticed some inconsistencies with how the DSL processes hooks while working on #3375, this was also opened as a split up prerequisite for #3377.

Ensures all hook DSL methods utilise #process_hooks + some minor changes (see comments).

Your checklist for this pull request

  • I have reviewed the guidelines for contributing to this repository.
  • I have added (or updated) appropriate tests if this PR fixes a bug or adds a feature.
  • My pull request is 100 lines added/removed or less so that it can be easily reviewed.
  • If this PR doesn't need tests (docs change), I added [ci skip] to the title of the PR.
  • If this closes any issues, I have added "Closes #issue" to the PR description or my commit messages.
  • I have updated the documentation accordingly.
  • All new and existing tests passed, including Rubocop.

@@ -731,6 +729,8 @@ def on_booted(&block)
# @version 5.0.0
#
def on_refork(key = nil, &block)
warn_if_in_single_mode('on_refork')
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this makes sense here? This seemed to be the only cluster mode related hook that was missing the warning.

Comment on lines -1207 to +1205
"so your `#{hook_name}` block did not run"
"so your `#{hook_name}` block will not run."
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This warning is displayed during configuration, so it makes more sense to tell the user that it will not run, as the hooks haven't actually been processed yet.

@joshuay03 joshuay03 force-pushed the consistent-dsl-hook-processing branch from 6692b90 to 7c6c31e Compare May 2, 2024 11:45
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added coverage for hooks missing in this suite.

@joshuay03
Copy link
Contributor Author

Note to self, related PR: #3380.

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.

None yet

1 participant