Mark Allen TSMMark

alias binding.pry as debugger in .pryrc pry config file

The Problem

In my experience, debugger is easier for people to remember and to type. And so most devs on our team prefer typing debugger over binding.pry. However, debugger is worse than binding.pry because it doesn't use Pry, which is better than standard byebug / irb repl.

The Solution

Alias binding.pry as debugger. Now we should be able to use debugger and binding.pry interchangeably, and it will always use Pry!

	const useYouTubeIframeAPIReady = (): boolean => {
	const [isReady, setIsReady] = useState<boolean>(false)

	useEffect(() => {
	if (window.YT.Player) {
	setIsReady(true)
	return
	}

	window['onYouTubeIframeAPIReady'] = () => {

	# Has kwargs? (Keyword arguments)
	def method_has_keyword_parameters?(method)
	method.parameters.any? do \|param\|
	type, _name = param

	type == :key
	end
	end

	# Has ordered arguments?

	# .github/workflows/update_with_latest_master.yml
	#
	# This is a Github Action Workflow to merge master into current branch when a label is added to a PR.
	# Label: `update with latest master`
	#
	# 1) Add this yml file to your github workflows directory.
	# 2) Add the issue/pr label: `update with latest master` to your project.
	# 3) Any time you want to merge master into a branch, just add the `update with latest master` label to it!
	#
	# NOTE: This will trigger a new commit on your branch, potentially triggering CI, and other workflows.

	// https://twitter.com/BenLesh/status/1435711312617746432
	const pipe = (start, ...fns) => fns.reduce((prev, fn) => fn(prev), start);

	// Example usage:
	// pipe(source, map(fn), filter(fn))