Thomas Klemm thomasklemm

Heroku Review Apps managed by GitHub Actions

This gist aims to provide a simple solution for managing Heroku Review Apps with GitHub Actions due to the security incident that continues to disrupt Heroku's GitHub integration.

.github
├── workflows
│   ├── heroku_review_app_create.yml
│   └── heroku_review_app_destroy.yml

How to deal with missing Heroku CI/CD and Review Apps

The reason for this

https://status.heroku.com/incidents/2413

In particular the update from 2022-04-26 23:54:00 UTC

For the protection of our customers, we will not be reconnecting to GitHub until we are certain that we can do so safely, **which may take some time

Descriptive messages with basic asserts

What if I told you that it's possible to get helpful failure messages from basic asserts using idiomatic equality == checks? No DSLs in sight.

This is a proof of concept to demonstrate that it's possible... mostly to satisfy my own curiosity. The concepts here could theoretically be expanded to provide a useful extension to existing testing frameworks or perhaps lay a foundation for an entirely new one.

This experiment created with Ruby 3.0.1. Note to self: There's probably a way to do this with TracePoint instead of monkey patching but I couldn't figure out how to get a reference to the passed variable being compared.

Examples:

Pure ESM package

The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.

This means you have the following choices:

Use ESM yourself. (preferred)
Use import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.
If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
Stay on the existing version of the package until you can move to ESM.

Sign in with Apple Implementation for Ruby on Rails

Note: Before diving into this implementation, consider that there are more popular and potentially easier-to-use solutions for implementing Sign in with Apple in Ruby on Rails, such as Omniauth. If you prefer a more out-of-the-box approach, explore those alternatives.

Overview

This implementation of the Sign in with Apple service in Ruby on Rails is suitable for APIs, eliminating the need for views.

	export function reduceToParams(elements) {
	return elements.reduce((hash, node) => Object.assign(hash, { [node.name]: node.value }), {})
	}

	export function stopEverything(e) {
	e.preventDefault()
	e.stopPropagation()
	e.stopImmediatePropagation()
	}

	# Add color coding based on Rails environment for safety

	if defined? Rails
	banner = if Rails.env.production?
	"\e[41;97;1m #{Rails.env} \e[0m "
	else
	"\e[42;97;1m #{Rails.env} \e[0m "
	end

	# Build a custom prompt

	import Amplify from 'aws-amplify';
	const { AppsyncCdkAppStack } = require('./outputs.json');
	import config from './aws-exports';

	Amplify.configure({
	...config,
	aws_appsync_graphqlEndpoint: AppsyncCdkAppStack.GraphQLAPIURL,
	aws_appsync_apiKey: AppsyncCdkAppStack.GraphQLAPIKey
	})

	%sl-alert.popup-toast{id: id, type: type, open: false, duration: duration, closable: true}
	%sl-icon{slot: "icon", name: icon}
	- if title.present?
	%strong= title
	%br

	= text

	class ApplicationController < ActionController::Base
	after_action :clear_view_component_cache, if: -> { Rails.env.development? }

	def clear_view_component_cache
	ViewComponent::CompileCache.cache = Set.new
	end
	end