Rubygems | Latest Versions for gr_autolinkhttps://rubygems.org/gems2023-09-29T17:58:32Zgr_autolink (1.0.13)https://rubygems.org/gems/gr_autolink/versions/1.0.132014-03-28T23:25:04ZAaron Patterson, Juanjo Bazan, Akira Matsuda, Brian Percival, Jonathan SchatzForked version of rails_autolink with new functionality
This is an adaptation of the extraction of the `auto_link` method from rails
that is the rails_autolink gem. The `auto_link`
method was removed from Rails in version Rails 3.1. This gem is meant to
bridge the gap for people migrating...and behaves a little differently from the
parent gem we forked from:
* performs html-escaping of characters such as '&' in strings that are getting
linkified if the incoming string is not html_safe?
* retains html-safety of incoming string (if input string is unsafe, will return
unsafe and vice versa)
* fixes at least one bug:
(<img src="http://some.u.rl"> => <img src="<a href="http://some.u.rl">http://some.u.rl</a>">)
though can't imagine this is intended behavior, also have trouble believing that
this was an open bug in rails...
gr_autolink (1.0.11)https://rubygems.org/gems/gr_autolink/versions/1.0.112012-04-18T01:31:10ZAaron Patterson, Juanjo Bazan, Akira Matsuda, Brian PercivalThis is an adaptation of the extraction of the `auto_link` method from rails that is the rails_autolink gem
This is an adaptation of the extraction of the `auto_link` method from rails
that is the rails_autolink gem. The `auto_link`
method was removed from Rails in version Rails 3.1. This gem is meant to
bridge the gap for people migrating...and behaves a little differently from the
parent gem we forked from:
* performs html-escaping of characters such as '&' in strings that are getting
linkified if the incoming string is not html_safe?
* retains html-safety of incoming string (if input string is unsafe, will return
unsafe and vice versa)
* fixes at least one bug:
(<img src="http://some.u.rl"> => <img src="<a href="http://some.u.rl">http://some.u.rl</a>">)
though can't imagine this is intended behavior, also have trouble believing that
this was an open bug in rails... gr_autolink (1.0.10)https://rubygems.org/gems/gr_autolink/versions/1.0.102012-04-02T18:41:26ZAaron Patterson, Juanjo Bazan, Akira Matsuda, Brian PercivalThis is an adaptation of the extraction of the `auto_link` method from rails that is the rails_autolink gem
This is an adaptation of the extraction of the `auto_link` method from rails
that is the rails_autolink gem. The `auto_link`
method was removed from Rails in version Rails 3.1. This gem is meant to
bridge the gap for people migrating...and behaves a little differently from the
parent gem we forked from:
* performs html-escaping of characters such as '&' in strings that are getting
linkified if the incoming string is not html_safe?
* retains html-safety of incoming string (if input string is unsafe, will return
unsafe and vice versa)
* fixes at least one bug:
(<img src="http://some.u.rl"> => <img src="<a href="http://some.u.rl">http://some.u.rl</a>">)
though can't imagine this is intended behavior, also have trouble believing that
this was an open bug in rails... gr_autolink (1.0.9)https://rubygems.org/gems/gr_autolink/versions/1.0.92012-03-31T04:42:57ZAaron Patterson, Juanjo Bazan, Akira Matsuda, Brian PercivalThis is an adaptation of the extraction of the `auto_link` method from rails that is the rails_autolink gem
This is an adaptation of the extraction of the `auto_link` method from rails
that is the rails_autolink gem. The `auto_link`
method was removed from Rails in version Rails 3.1. This gem is meant to
bridge the gap for people migrating...and behaves a little differently from the
parent gem we forked from:
* performs html-escaping of characters such as '&' in strings that are getting
linkified if the incoming string is not html_safe?
* retains html-safety of incoming string (if input string is unsafe, will return
unsafe and vice versa)
* fixes at least one bug:
(<img src="http://some.u.rl"> => <img src="<a href="http://some.u.rl">http://some.u.rl</a>">)
though can't imagine this is intended behavior, also have trouble believing that
this was an open bug in rails... gr_autolink (1.0.8)https://rubygems.org/gems/gr_autolink/versions/1.0.82012-03-31T00:58:06ZAaron Patterson, Juanjo Bazan, Akira Matsuda, Brian PercivalThis is an adaptation of the extraction of the `auto_link` method from rails that is the rails_autolink gem
This is an adaptation of the extraction of the `auto_link` method from rails
that is the rails_autolink gem. The `auto_link`
method was removed from Rails in version Rails 3.1. This gem is meant to
bridge the gap for people migrating...and behaves a little differently from the
parent gem we forked from:
* performs html-escaping of characters such as '&' in strings that are getting
linkified if the incoming string is not html_safe?
* retains html-safety of incoming string (if input string is unsafe, will return
unsafe and vice versa)
* fixes at least one bug:
(<img src="http://some.u.rl"> => <img src="<a href="http://some.u.rl">http://some.u.rl</a>">)
though can't imagine this is intended behavior, also have trouble believing that
this was an open bug in rails... gr_autolink (1.0.7)https://rubygems.org/gems/gr_autolink/versions/1.0.72012-03-31T00:14:05ZAaron Patterson, Juanjo Bazan, Akira Matsuda, Brian PercivalThis is an adaptation of the extraction of the `auto_link` method from rails that is the rails_autolink gem
This is an adaptation of the extraction of the `auto_link` method from rails
that is the rails_autolink gem. The `auto_link`
method was removed from Rails in version Rails 3.1. This gem is meant to
bridge the gap for people migrating...and behaves a little differently from the
parent gem we forked from:
* performs html-escaping of characters such as '&' in strings that are getting
linkified if the incoming string is not html_safe?
* retains html-safety of incoming string (if input string is unsafe, will return
unsafe and vice versa)
* fixes at least one bug:
(<img src="http://some.u.rl"> => <img src="<a href="http://some.u.rl">http://some.u.rl</a>">)
though can't imagine this is intended behavior, also have trouble believing that
this was an open bug in rails...