Patrick Ward patrickward

Steps to get started with Expo, Typescript, ESLint and Prettier

The first step is to use the Expo CLI to initialize the project. If you don't have the latest version of the Expo CLI tool, (or you don't have it installed) run npm install -g expo-cli.

Now run the following commands in the same order:

expo init my-app -t expo-template-blank-typescript
npx install-peerdeps --dev eslint-config-airbnb
npm i --save-dev @typescript-eslint/parser @typescript-eslint/eslint-plugin
npm i --save-dev prettier eslint-config-prettier eslint-plugin-prettier

Create or edit the file .eslintrc.json with the following content:

I'm a fan of MiniTest::Spec. It strikes a nice balance between the simplicity of TestUnit and the readable syntax of RSpec. When I first switched from RSpec to MiniTest::Spec, one thing I was worried I would miss was the ability to add matchers. (A note in terminology: "matchers" in MiniTest::Spec refer to something completely different than "matchers" in RSpec. I won't get into it, but from now on, let's use the proper term: "expectations").

Understanding MiniTest::Expectations

Let's take a look in the code (I'm specifically referring to the gem, not the standard library that's built into Ruby 1.9):

# minitest/spec.rb

module MiniTest::Expectations

	Latency Comparison Numbers (~2012)
	----------------------------------
	L1 cache reference 0.5 ns
	Branch mispredict 5 ns
	L2 cache reference 7 ns 14x L1 cache
	Mutex lock/unlock 25 ns
	Main memory reference 100 ns 20x L2 cache, 200x L1 cache
	Compress 1K bytes with Zippy 3,000 ns 3 us
	Send 1K bytes over 1 Gbps network 10,000 ns 10 us
	Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD

	---
	# ^^^ YAML documents must begin with the document separator "---"
	#
	#### Example docblock, I like to put a descriptive comment at the top of my
	#### playbooks.
	#
	# Overview: Playbook to bootstrap a new host for configuration management.
	# Applies to: production
	# Description:
	# Ensures that a host is configured for management with Ansible.

	// includes bindings for fetching/fetched

	PaginatedCollection = Backbone.Collection.extend({
	initialize: function() {
	_.bindAll(this, 'parse', 'url', 'pageInfo', 'nextPage', 'previousPage');
	this.page = 1;
	},
	fetch: function(options) {
	options \|\| (options = {});
	this.trigger("fetching");

	# autoload concerns
	module YourApp
	class Application < Rails::Application
	config.autoload_paths += %W(
	#{config.root}/app/controllers/concerns
	#{config.root}/app/models/concerns
	)
	end
	end

	//
	// Backbone.Rails.js
	//
	// Makes Backbone.js play nicely with the default Rails setup, i.e.,
	// no need to set
	// ActiveRecord::Base.include_root_in_json = false
	// and build all of your models directly from `params` rather than
	// `params[:model]`.
	//
	// Load this file after backbone.js and before your application JS.

	# RSpec 2.0 syntax Cheet Sheet by http://ApproachE.com

	# defining spec within a module will automatically pick Player::MovieList as a 'subject' (see below)
	module Player
	describe MovieList, "with optional description" do

	it "is pending example, so that you can write ones quickly"

	it "is already working example that we want to suspend from failing temporarily" do
	pending("working on another feature that temporarily breaks this one")