Bruno Michel

@ryanb : I've just created a bug report on lighthouse with a patch for this bug -> https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/3518-link_to-doesnt-escape-its-input . @minaguib : you can do that with: link_to x.html_safe!, comments_path Strings...

By the way, I've also found the same flaw on label_tag (https://rails.lighthouseapp.com/projects/8994/tickets/3449-label-tag-doesnt-escape-its-input ) and field_set_tag (https://rails.lighthouseapp.com/projects/8994/tickets/3450-field_set_tag-doesnt-escape-the-legend ).

I have a problem with button_to with the lastest 2-3-branch and http://github.com/rails/rails_xss: the button_to HTML code is escaped, so users see the HTML code instead of the button. There is...

By the way, in Rails 2.3, content_tag doesn't escape its input, neither do functions that use it like label_tag. In Rails 3.0, my patch for that was accepted: https://rails.lighthouseapp.com/projects/8994/tickets/3883-content_tag-does-not-escape-its-input. Do...

With the current 2-3-stable branch for rails and the latest version of rails/rails_xss, I have a popup if I use any of these lines:

I don't have a lot of experiences with functional programming, but the router makes me think to pattern matching: ```rust // users.gleam import midas fn list() -> midas.Response { //...

@rvagg can you update the compatibility table please?

Hi, thanks for your plugin. I can see you have put some basic type hint support, like you said. It bugs when we declare a return type for a function,...

Thanks! It looks like it works pretty well on my project.

Hello @aleroyer, thanks for the detailed report. I'm currently looking to improve the desktop client on windows. It will take some times as we need to change some deep dependencies.