A-J Roos Asjas

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

Installing V8 on a Mac

Prerequisites

Install Xcode (Avaliable on the Mac App Store)
Install Xcode Command Line Tools (Preferences > Downloads)
Install depot_tools
- $ git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git
- $ nano ~/.zshrc
- Add path=('/path/to/depot_tools' $path)

Project Title

One Paragraph of project description goes here

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

Prerequisites

Enable #enable-devtools-experiments flag in chrome://flags section.
Open Chorme Devtools and check Settings > Experiments > Allow extensions to load custom stylesheets.

Create the following four files in a dedicated folder.

3.1. devtools.html

<html>
<head></head>
<body><script src="devtools.js"></script></body>

Array Iteration

https://gist.github.com/ljharb/58faf1cfcb4e6808f74aae4ef7944cff

While attempting to explain JavaScript's reduce method on arrays, conceptually, I came up with the following - hopefully it's helpful; happy to tweak it if anyone has suggestions.

Intro

JavaScript Arrays have lots of built in methods on their prototype. Some of them mutate - ie, they change the underlying array in-place. Luckily, most of them do not - they instead return an entirely distinct array. Since arrays are conceptually a contiguous list of items, it helps code clarity and maintainability a lot to be able to operate on them in a "functional" way. (I'll also insist on referring to an array as a "list" - although in some languages, List is a native data type, in JS and this post, I'm referring to the concept. Everywhere I use the word "list" you can assume I'm talking about a JS Array) This means, to perform a single operation on the list as a whole ("atomically"), and to return a new list - thus making it mu

	<!-- Solution brought to you by Caroline Schnapp -->
	<!-- See this: https://docs.shopify.com/support/your-store/products/can-i-recommend-related-products#finding-a-relevant-collecitons -->

	{% comment %}
	Number of related items per row,
	and number of rows.
	{% endcomment %}

	{% assign number_of_related_products_per_row = 4 %}
	{% assign number_of_rows = 1 %}

	/* Sample JavaScript file added with ScriptTag resource.
	This sample file is meant to teach best practices.
	Your app will load jQuery if it's not defined.
	Your app will load jQuery if jQuery is defined but is too old, e.g. < 1.7.
	Your app does not change the definition of $ or jQuery outside the app.
	Example: if a Shopify theme uses jQuery 1.4.2, both of these statements run in the console will still return '1.4.2'
	once the app is installed, even if the app uses jQuery 1.9.1:
	jQuery.fn.jquery => "1.4.2"
	$.fn.jquery -> "1.4.2"
	*/

	# Backup
	docker exec CONTAINER /usr/bin/mysqldump -u root --password=root DATABASE > backup.sql

	# Restore
	cat backup.sql \| docker exec -i CONTAINER /usr/bin/mysql -u root --password=root DATABASE

	#!/bin/bash
	files=$(git diff --cached --name-only \| grep '\.jsx\?$')

	# Prevent ESLint help message if no files matched
	if [[ $files = "" ]] ; then
	exit 0
	fi

	failed=0
	for file in ${files}; do

	// See http://rosskendall.com/blog/web/javascript-function-to-check-an-email-address-conforms-to-rfc822

	function isEmail(email){

	return /^([^\x00-\x20\x22\x28\x29\x2c\x2e\x3a-\x3c\x3e\x40\x5b-\x5d\x7f-\xff]+\|\x22([^\x0d\x22\x5c\x80-\xff]\|\x5c[\x00-\x7f])\x22)(\x2e([^\x00-\x20\x22\x28\x29\x2c\x2e\x3a-\x3c\x3e\x40\x5b-\x5d\x7f-\xff]+\|\x22([^\x0d\x22\x5c\x80-\xff]\|\x5c[\x00-\x7f])\x22))\x40([^\x00-\x20\x22\x28\x29\x2c\x2e\x3a-\x3c\x3e\x40\x5b-\x5d\x7f-\xff]+\|\x5b([^\x0d\x5b-\x5d\x80-\xff]\|\x5c[\x00-\x7f])\x5d)(\x2e([^\x00-\x20\x22\x28\x29\x2c\x2e\x3a-\x3c\x3e\x40\x5b-\x5d\x7f-\xff]+\|\x5b([^\x0d\x5b-\x5d\x80-\xff]\|\x5c[\x00-\x7f])\x5d))$/.test( email );
	}