Joe Krump joekrump

My VS Code extensions

code --install-extension NuclleaR.vscode-extension-auto-import
code --install-extension dbaeumer.vscode-eslint
code --install-extension dzannotti.vscode-babel-coloring
code --install-extension eg2.tslint
code --install-extension passionkind.prettier-vscode-with-tabs

Extensions

Generated by running code --list-extensions

2gua.rainbow-brackets
andys8.jest-snippets
ChakrounAnas.turbo-console-log
christian-kohler.path-intellisense
dbaeumer.vscode-eslint
DotJoshJohnson.xml

Tests

Open Segment to view events fired from beta instances.
Log into this beta using email address [email protected] ...
On the Segment debugger page, a new "page" event has been received.
Click on the event in the list
In the panel that opens on the right, click on the "Raw" tab.
Within the data of properties, the data for url contains a path that has a value that is correct and not equal to "REDACTED".

FEI Team Demo - Apollo Feature Flags

Important URLs:

http://localhost:3000/admin/accounts/2 > "Features" tab http://localhost:3000/admin/tasks > > "Set Feature Flags For Accounts"

Files

pricing_tiers.yml - Where FFs are defined

Listeners registered to scopes and elements are automatically cleaned up when they are destroyed, but if you registered a listener on a service, or registered a listener on a DOM node that isn’t being deleted, you’ll have to clean it up yourself or you risk introducing a memory leak.

Best Practice: Components should clean up after themselves. You can use the $onDestroy() AngularJS component lifecycle hook to run a clean-up function when the component is removed. An older way of doing this would have been to add an event handler for element.on('$destroy', …) or scope.$on('$destroy', …) for an AngularJS Directive.

Question:

I have a

element.on("click", (event) => {...});

>```

Closures

Asynchronous JavaScript

Microtasks Queues and Schedules

	#!/usr/bin/env ruby

	directory = ARGV[0] \|\| './client-src'
	file_extension = ARGV[1] \|\| '.coffee'

	def get_matching_files_in(directory, file_extension)
	manage_ui_files = []
	accounting_files = []
	payment_files = []
	billing_files = []

	{
	// Place your global snippets here. Each snippet is defined under a snippet name and has a scope, prefix, body and
	// description. Add comma separated ids of the languages where the snippet is applicable in the scope field. If scope
	// is left empty or omitted, the snippet gets applied to all languages. The prefix is what is
	// used to trigger the snippet and the body will be expanded and inserted. Possible variables are:
	// $1, $2 for tab stops, $0 for the final cursor position, and ${1:label}, ${2:another} for placeholders.
	// Placeholders with the same ids are connected.
	// Example:
	"Print to console": {
	"scope": "javascript,typescript",