| # I struggled with getting a fading flash[:notice] that would work both with standard served pages as well | |
| # as ajax requests. I saw a number of posts online but did not have luck with or they seemed too | |
| # complicated. This is what I ended up with from experimentation. | |
| # Place the following code in application_helper.rb. Note that you need to either change or name your | |
| # containers as I have in this code: | |
| # application_helper.rb | |
| module ApplicationHelper | |
| # model file | |
| class User < ActiveRecord::Base | |
| has_many :books | |
| accepts_nested_attributes_for :books, :reject_if => lambda {|book| book[:name].blank? }, :allow_destroy => true | |
| end | |
| # :reject_if => it passes the whole hash passed from browser with book details into this Proc(lambda) and iterates over each book hash. The book record is not created if the condition given in the lambda block is satisfied. | |
| # :allow_destroy => if set to true, then the book record that was passed from browser, while submitting User form, with a key-value pair :_destroy => 1 (or '1' or true or "true") will be destroyed |
| # This is a skeleton for testing models including examples of validations, callbacks, | |
| # scopes, instance & class methods, associations, and more. | |
| # Pick and choose what you want, as all models don't NEED to be tested at this depth. | |
| # | |
| # I'm always eager to hear new tips & suggestions as I'm still new to testing, | |
| # so if you have any, please share! | |
| # | |
| # @kyletcarlson | |
| # | |
| # This skeleton also assumes you're using the following gems: |
| # Read about the yield keyword and ruby blocks. | |
| # http://allaboutruby.wordpress.com/2006/01/20/ruby-blocks-101/ | |
| # http://ruby.about.com/od/beginningruby/a/Block-Parameters-And-Yielding.htm | |
| # http://blog.codahale.com/2005/11/24/a-ruby-howto-writing-a-method-that-uses-code-blocks/ | |
| # http://www.robertsosinski.com/2008/12/21/understanding-ruby-blocks-procs-and-lambdas/ | |
| # Now that you know how the yield method works, try to write your | |
| # own version of the each method without using the each method | |
| # provided by ruby. As in, try to build my_each using only the |
People
 :bowtie: |
😄 :smile: |
😆 :laughing: |
|---|---|---|
😊 :blush: |
😃 :smiley: |
:relaxed: |
😏 :smirk: |
😍 :heart_eyes: |
😘 :kissing_heart: |
😚 :kissing_closed_eyes: |
😳 :flushed: |
😌 :relieved: |
😆 :satisfied: |
😁 :grin: |
😉 :wink: |
😜 :stuck_out_tongue_winking_eye: |
😝 :stuck_out_tongue_closed_eyes: |
😀 :grinning: |
😗 :kissing: |
😙 :kissing_smiling_eyes: |
😛 :stuck_out_tongue: |
Scenario: You deployed a Heroku project that contains sensitive data (password, API key, etc) but you want to share it on Github.
Problem: You need to commit all files necessary for the application to run on Heroku. However, pushing this to Github would reveal the sensitive info.
Solution: Have a production branch (for this example, master will be the production branch) and a Github branch. The latter contains a different .gitignore that ignores the sensitive files.
| # Terminal Cheat Sheet | |
| pwd # print working directory | |
| ls # list files in directory | |
| cd # change directory | |
| ~ # home directory | |
| .. # up one directory | |
| - # previous working directory | |
| help # get help | |
| -h # get help |
Before doing anything, please check the versions of the gem files:
gem 'rails', '~> 5.1.4'
gem 'devise', '~> 4.4.0'Disclaimer - This solution may not work with older versions of rails and devise. Versions listed above were the latest versions of gems which I was using at the time of creation and tests. (10 Jan 2018)