dalezak

<div class="form-group">
  <%= form.label :type, "Type", class: "font-weight-bold" %>
  <%= form.select :type, ['TextQuestion', 'UrlQuestion'], { include_blank: true }, { class: "form-control", data: { action: "input->toggle#changed", target: "toggle.select" } } %>
</div>
<div class="form-group">
  <%= form.label :name, "Name", class: "font-weight-bold" %>
  <%= form.text_field :name, class: "form-control" %>
</div>
<div class="form-group" data-target="toggle.element" data-values="UrlQuestion">
  <%= form.label :url, "URL", class: "font-weight-bold" %>

yshmarov

# All AWS C9 envments
https://eu-central-1.console.aws.amazon.com/cloud9/home?region=us-east-1

# Instance management
https://console.aws.amazon.com/ec2/home?region=eu-central-1#Instances:sort=instanceId

# Create AWS C9 environment
https://eu-central-1.console.aws.amazon.com/cloud9/home/create

Setting - set tabs to 2

leastbad

This is all you really need to know in order to make Action Mailbox work in development.

1. Fire up ngrok http 3000 and make note of your subdomain for steps 3 and 8.
2. Create a Mailgun account because they offer sandbox addresses; grab your domain from the Dashboard.
3. Go into Receiving and create a catch-all route pointing to: https://XXX.ngrok.io/rails/action_mailbox/mailgun/inbound_emails/mime
4. Add your Mailgun API key to your credentials:

action_mailbox:
 mailgun_api_key: API KEY HERE

yunusemredilber

<!-- Some form -->  
  <div data-controller="auto-grow-textarea">
    <%= form.text_area :body, cols: 20, row: 2, placeholder: 'Bir yorum yazın...', class:'form-control', data: { action: 'input->auto-grow-textarea#resize', target: 'auto-grow-textarea.input' } %>
  </div>
<!-- Some form continued --> 

mlanett

HTTP status code symbols for Rails

Thanks to Cody Fauser for this list of HTTP responce codes and their Ruby on Rails symbol mappings.

Status Code Symbol
1xx Informational
100 :continue
101 :switching_protocols
102 :processing

brunopgalvao

<%= form_for @person do |f| %>
  <%= f.label :first_name, "First Name" %>:
  <%= f.text_field :first_name, list: 'first-name' %>
  <datalist id="first-name">
    <% Person.all.each do |person| %>
      <option value="<%= person.first_name %>"></option>
    <% end %>
  </datalist>
  <%= f.submit %>
<% end %>

tomas-stefano

Capybara Actions

# Anchor
click_link 'Save'

# Button
click_button 'awesome'

# Both above

nathancolgate

# Add these two gems
gem 'ice_cube',                     '0.9.3'
gem 'squeel',                       '1.0.16'

whitingx

Copied from http://code.lancepollard.com/complete-list-of-html-meta-tags/

Basic HTML Meta Tags

<meta charset='UTF-8'>
<meta name='keywords' content='your, tags'>
<meta name='description' content='150 words'>
<meta name='subject' content='your website's subject'>
<meta name='copyright' content='company name'>

jcasimir

Managing the Flash

HTTP is a stateless protocol. The server, generally speaking, has no idea if request number 243 came from the same user as request number 236. That's beautiful and, at the same time, annoying.

In the context of web applications we frequently want to persist state between requests. That might mean something like a shopping cart that follows a user through the online store, but it can be as simple as a status message.

In modern applications users expect feedback. They click a delete link and they expect to no just see the item disappear, they'll expect a "Item Deleted" message. In Rails we handle these messages using the flash.

Flash as Hash