From: s@sikac.hu
To: ruby-core@ruby-lang.org
Subject: [ruby-core:71658] [Ruby trunk - Feature #11735] [Open] Porting String#squish and String#squish! from Ruby on Rails' Active Support
Date: Tue, 24 Nov 2015 19:36:34 +0000 [thread overview]
Message-ID: <redmine.issue-11735.20151124193633.7c05ca2b69620132@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-11735.20151124193633@ruby-lang.org
Issue #11735 has been reported by Prem Sichanugrist.
----------------------------------------
Feature #11735: Porting String#squish and String#squish! from Ruby on Rails' Active Support
https://bugs.ruby-lang.org/issues/11735
* Author: Prem Sichanugrist
* Status: Open
* Priority: Normal
* Assignee:
----------------------------------------
Hi,
I have been using this `String#squish` method so many time when I'm using Rails, and I think it should be a useful addition to core.
This method is very useful when you have to write a multi-line string using heredoc, but you actually does not care about the white-spaces before, after, and in-between the string.
For example:
~~~
<<-SQL.squish
SELECT *
FROM users
WHERE users.username = 'sikachu'
SQL
#=> "SELECT * FROM users WHERE users.username='sikachu'"
~~~
Another example usage is when you are on the project that have a line length code standard, and you have to write a long warning message that needs to be printed to stdout:
~~~
puts <<-WARNING.squish
Unable to connect to the server. Please double-check that you are currently
connecting to the internet and your proxy server is working.
WARNING
#=> Unable to connect to the server. Please double-check that you are currently connecting to the internet and your proxy server is working.
~~~
By the way, this is my first patch and my first time writing something in C, so there might be something that does not look right to you. I'll happy to revise this patch (and learn about C in the process!) from your feedback.
Thank you,
Prem
---Files--------------------------------
0001-Introduce-String-squish-and-String-squish.patch (4.67 KB)
--
https://bugs.ruby-lang.org/
next parent reply other threads:[~2015-11-24 19:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-11735.20151124193633@ruby-lang.org>
2015-11-24 19:36 ` s [this message]
2015-11-24 20:40 ` [ruby-core:71663] Re: [Ruby trunk - Feature #11735] [Open] Porting String#squish and String#squish! from Ruby on Rails' Active Support Eric Wong
2015-11-24 19:38 ` [ruby-core:71659] [Ruby trunk - Feature #11735] " s
2015-11-24 19:42 ` [ruby-core:71660] " s
2015-11-25 4:20 ` [ruby-core:71676] " nobu
2015-11-25 17:03 ` [ruby-core:71685] " deivid.rodriguez
2015-12-07 7:50 ` [ruby-core:71890] " ko1
2015-12-07 7:51 ` [ruby-core:71891] " nobu
2015-12-07 14:19 ` [ruby-core:71906] " s
2016-05-18 1:22 ` [ruby-core:75589] [Ruby trunk Feature#11735] " shyouhei
2016-05-19 17:57 ` [ruby-core:75616] " amd
2016-05-20 2:38 ` [ruby-core:75631] " shyouhei
2016-06-23 17:33 ` [ruby-core:76120] " amd
2016-06-24 8:02 ` [ruby-core:76134] " shyouhei
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.issue-11735.20151124193633.7c05ca2b69620132@ruby-lang.org \
--to=ruby-core@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 read-only IMAP folder(s) and NNTP newsgroup(s).