ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "nobu (Nobuyoshi Nakada) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "nobu (Nobuyoshi Nakada)" <noreply@ruby-lang.org>
Subject: [ruby-core:123246] [Ruby Feature#21556] Add true? and false? methods to NilClass, TrueClass, FalseClass, and String
Date: Sun, 14 Sep 2025 01:35:02 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-114579.20250914013502.59013@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-21556.20250829172810.59013@ruby-lang.org>

Issue #21556 has been updated by nobu (Nobuyoshi Nakada).


Phalado (Raphael Cordeiro) wrote in #note-6:
> The idea here came when working with JSON from requests and, especially, Active Admin. Users sometimes fill boolean values as true, other times as "true", which can be a problem if you are expecting a boolean or a string specifically. Also, a nil value can be considered 'false', which is not always the case when treating data.

It sounds like that this is an issue specific to Active Admin.
Please tell them, instead of Ruby.

----------------------------------------
Feature #21556: Add true? and false? methods to NilClass, TrueClass, FalseClass, and String
https://bugs.ruby-lang.org/issues/21556#change-114579

* Author: Phalado (Raphael Cordeiro)
* Status: Feedback
----------------------------------------
Sometimes we need to check for an exact `true` or `false` value. This can be a string or a boolean value.

Usually, what I do to solve this is something like `value.to_s == true`, this way covering for strings, booleans, and nil values.

The idea of these new methods is to check for the exact value, being it a String, a Boolean, or even a Nil value.

This is the result obtained:

``` ruby
# String

'true'.true? # true
'false'.true? # false
''.true? # false

'true'.false? # false
'false'.false? # true
''.false? # false

# Boolean

true.true? # true
true.false? # false

false.true? # false
false.false? # true

# Nil

nil.true? # false
nil.false? # false
```




-- 
https://bugs.ruby-lang.org/
______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/

      parent reply	other threads:[~2025-09-14  1:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-29 17:28 [ruby-core:123122] " Phalado (Raphael Cordeiro) via ruby-core
2025-08-29 22:50 ` [ruby-core:123129] " nobu (Nobuyoshi Nakada) via ruby-core
2025-08-30 22:58 ` [ruby-core:123139] " Phalado (Raphael Cordeiro) via ruby-core
2025-08-31  0:00 ` [ruby-core:123140] " austin (Austin Ziegler) via ruby-core
2025-09-01  0:54 ` [ruby-core:123149] " shan (Shannon Skipper) via ruby-core
2025-09-01 13:44 ` [ruby-core:123157] " Phalado (Raphael Cordeiro) via ruby-core
2025-09-01 13:50 ` [ruby-core:123158] " Phalado (Raphael Cordeiro) via ruby-core
2025-09-14  1:30 ` [ruby-core:123245] " nobu (Nobuyoshi Nakada) via ruby-core
2025-09-14  1:35 ` nobu (Nobuyoshi Nakada) via ruby-core [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-114579.20250914013502.59013@ruby-lang.org \
    --to=ruby-core@ml.ruby-lang.org \
    --cc=noreply@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).