Jeb Coleman el-feo

First couple things I thought about when migrating after reading the docs

So migrating my existing app wasn't as troublesome as I originally thought. First thing I did was take a look at my router and routes and figure try to make a mental model of all the files where I had nested routes in the existing app because those components/containers will contain {this.props.children}. So I need to replace those with the nested <Match /> components.

So just to give an example:

In v2:

<Router history={history}>
  <Route path="/" component={App}>

Moved to Shopify/graphql-design-tutorial

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

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

action_mailbox:
 mailgun_api_key: API KEY HERE

Rails 7 new features. Before and After

Add ComparisonValidator
PostgreSQL generated columns
PostgreSQL custom enum types
Add tracking of belongs_to association
association_previously_changed? method
Add invert_where method
Add associated method
Add missing method
Active Record Encryption

	<% # app/views/layouts/admin.html.erb %>

	<!DOCTYPE html>
	<html>
	<head>
	<title>Admin Interface</title>
	<%= csrf_meta_tags %>

	<% # Optionally use admin-specific assets here instead of the normal application assets %>
	<%= stylesheet_link_tag 'admin', media: 'all', 'data-turbolinks-track': 'reload' %>

	# The following comments fill some of the gaps in Solargraph's understanding of
	# Rails apps. Since they're all in YARD, they get mapped in Solargraph but
	# ignored at runtime.
	#
	# You can put this file anywhere in the project, as long as it gets included in
	# the workspace maps. It's recommended that you keep it in a standalone file
	# instead of pasting it into an existing one.
	#
	# @!parse
	# class ActionController::Base

	apiVersion: v1
	kind: ConfigMap
	metadata:
	name: example
	namespace: default
	data:
	APPLICATION_HOST: example.com
	LANG: en_US.UTF-8
	PIDFILE: /tmp/server.pid
	PORT: "3000"

	javascript: Promise.all([import('https://unpkg.com/[email protected]?module'), import('https://unpkg.com/@tehshrike/[email protected]'), ]).then(async ([{
	default: Turndown
	}, {
	default: Readability
	}]) => {

	/* Optional vault name */
	const vault = "";

	/* Optional folder name such as "Clippings/" */

	resources :media, shallow: true,
	constraints: ->(req) do
	current_user = req.env["warden"].user(:user)
	Flipper.enabled?(:media_uploads, current_user)
	end

	# Ruby pattern matching based on Type (=> operator)
	[1,2,3] => [1, Integer, my_variable]
	# This means:
	# We want to assign `my_variable` (variable binding),
	# but only if the first position is 1 and second position is an Integer)
	my_variable # => 3 ✨

	# What if it doesn't match? You get an exception 💣
	[1,2,3] => [Integer, String, my_variable]
	# [1, 2, 3]: String === 2 does not return true (NoMatchingPatternError)