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

IRB.conf[:SAVE_HISTORY] should handle boolean values #1062

Merged
merged 1 commit into from
Jan 11, 2025
Merged

Conversation

st0012
Copy link
Member

@st0012 st0012 commented Jan 11, 2025

Although not documented, IRB.conf[:SAVE_HISTORY] used to accept boolean, which now causes NoMethodError when used.

This commit changes the behavior to accept boolean values and adds tests for the behavior.

Closes #1058

Although not documented, `IRB.conf[:SAVE_HISTORY]` used to accept boolean,
which now causes `NoMethodError` when used.

This commit changes the behavior to accept boolean values and
adds tests for the behavior.
@st0012 st0012 added the bug Something isn't working label Jan 11, 2025
@st0012 st0012 mentioned this pull request Jan 11, 2025
@tompng tompng merged commit 8b1a07b into master Jan 11, 2025
67 checks passed
@tompng tompng deleted the fix-#1058 branch January 11, 2025 14:03
matzbot pushed a commit to ruby/ruby that referenced this pull request Jan 11, 2025
(ruby/irb#1062)

Although not documented, `IRB.conf[:SAVE_HISTORY]` used to accept boolean,
which now causes `NoMethodError` when used.

This commit changes the behavior to accept boolean values and
adds tests for the behavior.

ruby/irb@8b1a07b2a8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

Successfully merging this pull request may close these issues.

Disable save history
2 participants