Dmitry Salnikov dmitry-salnikov

MacOS X + oh my zsh + powerline fonts + visual studio code (vscode) terminal settings

Thank you everybody, Your comments makes it better

Install oh my zsh

sh -c "$(curl -fsSL https://raw.github.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"

The unknown-prop warning will fire if you attempt to render a DOM element with a prop that is not recognized by React as a legal DOM attribute/property. You should ensure that your DOM elements do not have spurious props floating around.

There are a couple of likely reasons this warning could be appearing:

Are you using {...this.props} or cloneElement(element, this.props)? Your component is transferring its own props directly to a child element (eg. https://facebook.github.io/react/docs/transferring-props.html). When transferring props to a child component, you should ensure that you are not accidentally forwarding props that were intended to be interpreted by the parent component.
You are using a non-standard DOM attribute on a native DOM node, perhaps to represent custom data. If you are trying to attach custom data to a standard DOM element, consider using a custom data attribute (https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Using_data_attributes).
React does not yet reco

From an appropriate location:

mkdir replica-set
mkdir -p replica-set/rs0-0 replica-set/rs0-1
mongod --port 27018 --dbpath replica-set/rs0-0 --replSet rs0 --smallfiles --oplogSize 128 &
mongod --port 27019 --dbpath replica-set/rs0-1 --replSet rs0 --smallfiles --oplogSize 128 &
mongo localhost:27018

	### I. Setup
	apt-get install -y \
	ca-certificates \
	curl \
	gnupg \
	lsb-release \
	&& curl -fsSL https://download.docker.com/linux/ubuntu/gpg \| gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg \
	&& echo \
	"deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu \
	$(lsb_release -cs) stable" \| tee /etc/apt/sources.list.d/docker.list > /dev/null \

	import React from 'react'
	import hoistNonReactStatics from 'hoist-non-react-statics'
	import { assoc, assocPath, identity, is, map, prop } from 'ramda'
	import isValid from './isValid'

	// random helper function
	// extract the needed information from the event
	const getValueName = (e) => {
	const target = e.target
	const name = target.name

	import { Pipe, PipeTransform } from '@angular/core';

	const ordinals: string[] = ['th','st','nd','rd'];

	/*
	* Append ordinal to number (e.g. "1st" position)
	* Usage:
	* value \| ordinal:keepNumber
	* Example:
	* {{ 23 \| ordinal}}

	defaults delete com.apple.dt.Xcode
	rm -rf $HOME/Library/Application Support/Developer/Shared/Xcode
	rm -rf $HOME/Library/Saved\ Application\ State/com.apple.dt.Xcode.savedState
	rm -rf $HOME/Library/Preferences/com.apple.dt.Xcode.*
	xcrun simctl erase all
	xcrun simctl list \| grep -oh '[A-Z0-9]\{8\}-[A-Z0-9]\{4\}-[A-Z0-9]\{4\}-[A-Z0-9]\{4\}-[A-Z0-9]\{12\}' \| xargs -n1 xcrun simctl delete

	package <your_package>;

	import android.support.test.espresso.intent.rule.IntentsTestRule;
	import android.support.test.runner.AndroidJUnit4;
	import android.test.suitebuilder.annotation.LargeTest;

	import org.junit.After;
	import org.junit.Rule;
	import org.junit.Test;
	import org.junit.runner.RunWith;

	<!--
	This disables app transport security and allows non-HTTPS requests.
	Note: it is not recommended to use non-HTTPS requests for sensitive data. A better
	approach is to fix the non-secure resources. However, this patch will work in a pinch.

	To apply the fix in your Ionic/Cordova app, edit the file located here:

	platforms/ios/MyApp/MyApp-Info.plist

	And add this XML right before the end of the file inside of the last </dict> entry:

	{...
	"scripts": {
	"postinstall": "node patch.js",
	...
	}
	}