<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>rails on Sai Ram&#39;s Blog</title>
    <link>https://sairam.dev/tags/rails/</link>
    <description>Recent content in rails on Sai Ram&#39;s Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>&amp;copy; 2020. All rights reserved.</copyright>
    <lastBuildDate>Sat, 20 May 2017 18:00:00 +0530</lastBuildDate>
    
	<atom:link href="https://sairam.dev/tags/rails/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Using Rails with webpack generated assets</title>
      <link>https://sairam.dev/post/using-rails-with-webpack-assets/</link>
      <pubDate>Sat, 20 May 2017 18:00:00 +0530</pubDate>
      
      <guid>https://sairam.dev/post/using-rails-with-webpack-assets/</guid>
      <description>Our team started using webpack with Rails. Referencing/Sharing asset information from webpack to Rails is the problem being solved in this post. We want to use the webpack assets that are exposed in our Rails app. Not setting up a new plugin for uploading the generated assets would be a plus.
Our team used webpack to compile javascript and related assets. (If you are trying to learn webpack, note that it has a very steep learning curve).</description>
    </item>
    
    <item>
      <title>Identifying Bad Tests</title>
      <link>https://sairam.dev/post/2017-04-11-identifying-bad-tests/</link>
      <pubDate>Tue, 11 Apr 2017 22:00:00 +0530</pubDate>
      
      <guid>https://sairam.dev/post/2017-04-11-identifying-bad-tests/</guid>
      <description>Look at this code Rails FactoryGirl definition for a regular user class
FactoryGirl.define do factory :user do first_name &amp;#34;John&amp;#34; last_name &amp;#34;Doe&amp;#34; subscription_end_date Date.parse(&amp;#34;2019-01-01&amp;#34;) end end Does not look harmful. This is a base model. When your other spec files start using it, everything will work fine when you evaluate the subscription_end_date with other fields, but, exactly after 2019-01-01, on 2nd Jan 2019, the tests dependent on this value will start failing.</description>
    </item>
    
    <item>
      <title>How to Track User Agreement Acceptance in Database</title>
      <link>https://sairam.dev/post/how-to-track-user-agreement-acceptance-in-db/</link>
      <pubDate>Mon, 10 Apr 2017 22:30:00 +0530</pubDate>
      
      <guid>https://sairam.dev/post/how-to-track-user-agreement-acceptance-in-db/</guid>
      <description>Problem Statement How would you model to check if a user has accepted your &amp;ldquo;Terms and Conditions&amp;rdquo; or &amp;ldquo;COPPA&amp;rdquo; when building your website? Lets talk how would you track in your data store (MySQL or Postgres or Mongo DB).
The front-end is represented by a checkbox or click of a button &amp;lsquo;I Accept&amp;rsquo;, this translates to either a true or false and gets stored into the a column in the users table in your database which is a boolean field.</description>
    </item>
    
    <item>
      <title>Open Source Contribution to Spree/Solidus</title>
      <link>https://sairam.dev/post/2015-12-30-opensource-contribution/</link>
      <pubDate>Wed, 30 Dec 2015 23:00:00 +0530</pubDate>
      
      <guid>https://sairam.dev/post/2015-12-30-opensource-contribution/</guid>
      <description>This was one of the open source contribution in 2015 to a major Rails project used by e-commerce companies.
It usually takes hours/days to understand the basic framework, goals, motivations, features vs limitations etc., to start contributing to an open source project based on the amount of domain knowledge (especially for matured projects).
Its usually hard to find and understand bugs in a very well mature framework or language. One of the good things about using open source libraries is you get to know both the code and get to know the eco system while getting paid on the job.</description>
    </item>
    
  </channel>
</rss>