Ruby on Rails
Tuesday, January 7, 2020
On Sunday, January 5, 2020 at 8:41:33 AM UTC-5, Ariel Juodziukynas wrote:
No, the first line is ruby and the convention is snakecase so it's ok you use underscores, the second line is html and the attributes syntax is hyphen, when you access that data attribute with javascript it will be dataset.conversationWithId as camelcase. You should write using the convention of the language you are using, then each language takes care of converting it.El dom., 5 ene. 2020 a las 4:35, fugee ohu (<fuge...@gmail.com>) escribió:--<%= content_tag :div, id: "message_holder", data: {conversation_with_id: @conversation_with.id} do %>translates to this html from page source:<div id="message_holder" data-conversation-with-id="3">
The underscores get translated to hyphens Should I just rename the variable to conversation-with-id ?
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonra...@googlegroups.com .
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/ .8da006ce-97eb-49d2-aa3f- b2226c8f0ef5%40googlegroups. com
>> No, the first line is Ruby ... The second line is html
Can you please show me the first and second lines that refers to, I see you gave me the answer but I forgot what was the question
Also when javascript is included on the html.erb page in <script> containers then I can use <%= @some_data_here %> but when javascript is in a separate file I can't use that method unless I rename the file to js.erb ?
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/af19ed99-9508-4a31-9fa3-fa343c1451d2%40googlegroups.com.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment