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

Add assertion for dynamic_prompt's assertion execution #586

Merged
merged 1 commit into from
May 20, 2023

Conversation

st0012
Copy link
Member

@st0012 st0012 commented May 20, 2023

Because the assertions for dynamic_prompt lives inside a block given to RubyLex, they could be skipped unnoticed if the setup is not correct.

This commit adds a simple assertion to check if the block was actually executed.

Because the assertions for `dynamic_prompt` lives inside a block given to
`RubyLex`, they could be skipped unnoticed if the setup is not correct.

This commit adds a simple assertion to check if the block was actually
executed.
@st0012 st0012 self-assigned this May 20, 2023
Copy link
Member

@tompng tompng left a comment

Choose a reason for hiding this comment

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

👍

@tompng tompng merged commit bb68645 into master May 20, 2023
@tompng tompng deleted the improve-dynamic-prompt-assertion branch May 20, 2023 04:28
matzbot pushed a commit to ruby/ruby that referenced this pull request May 20, 2023
(ruby/irb#586)

Because the assertions for `dynamic_prompt` lives inside a block given to
`RubyLex`, they could be skipped unnoticed if the setup is not correct.

This commit adds a simple assertion to check if the block was actually
executed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants