Share this postWeekly bookmarks - Issue #3dcyoungdev.substack.comCopy linkFacebookEmailNoteOtherWeekly bookmarks - Issue #3DavidMay 13, 2022ShareGetting the feedback you need from colleagues and friendsIn the model-view-controller pattern that Rails is built on, it’s pretty clear what views and controllers are, but models are a little less clear. In my 10 years with Rails I’ve had the opportunity to come across a number of different conceptions regarding what models are. These conceptions often overlap but often don’t share the […]When testing the outcome of nested rollbacks, we explicitly told a class to receive(:end!).and_raise(ActiveRecord::RecordNotSaved) to emulate a deep failure in our transactions.There are some changes being proposed regarding viewport units, finally solving that "100vh in Safari on iOS" issue …Developers often reach for UI frameworks like Bootstrap or Material UI, hoping that they’ll save a bunch of time and quickly build a professional-looking app. Unfortunately, things rarely work out this way. Let’s talk about it.Emmet is labeling itself as the essential toolkit for web developers. It sure comes with some handy functions to drastically speed up your coding. If you’re a web developer, you’ve probably one way…An overview of time zones in Rails.Building the system architecture your teams needorginially posted by @thatmoodyguy on Exploring Ruby If you’re using the Devise gem to handle authentication duties for your application, you going to need a way to determine what happens after the user signs in, signs up, or signs out of your application. Devise provides a means to do this with the after_sign_in_path_for, after_sign_up_path_for, and after_sign_out_path_for methods. Simply override these methods with your own methods of the same name in your ApplicationController, and you’re all set. Except there’s a catch. Overriding after_sign_in_path_for and after_sign_out_path_for in ApplicationController will work, but if you override after_sign_up_path_for, it won’t work. It turns out that you need to override the RegistrationsController class, and override the method inside that controller. Your new controller will look something like this: ```ruby class RegistrationsController < Devise::RegistrationsController def create super end protectedHave you ever wanted to accept payments in Rails? With Stripe Checkout, it's never been easier. Jeffrey Morhous shows us how.Search analytics made easy. Contribute to ankane/searchjoy development by creating an account on GitHub.Hello everyone! I’ve just finished off this week’s work of building a fitness web app to helps users schedule workout sessions and manage routines. As a big fan of classy design, I insisted upon…