https://play.google.com/intl/en_us/badges/
npm install
npm run dl-badges
/** | |
*Submitted for verification at Etherscan.io on 2021-04-22 | |
*/ | |
// File: @openzeppelin/contracts/utils/Context.sol | |
// SPDX-License-Identifier: MIT | |
pragma solidity >=0.6.0 <0.8.0; |
# Removes all the merged branches, ignoring master and staging branches. | |
git branch --merged | grep -vE '^\*|master$|staging$' | xargs -I % git branch -d % |
/** | |
* Daisy chaining delays (setTimeout) using Promises | |
* | |
* Ex: delay(func1, 1000).delay(func2, 1000).delay(func3, 1000); | |
* | |
* @param {Function} cb - Callback function | |
* @param {Number} ms - Time delay (in milliseconds) | |
* @return chainable delay Promise (ie. delay(cb, ms).delay(cb, ms).delay(cb, ms)...) | |
* | |
* @see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Using_promises#Creating_a_Promise_around_an_old_callback_API |
https://play.google.com/intl/en_us/badges/
npm install
npm run dl-badges
import { Injectable } from '@angular/core'; | |
import { BehaviorSubject } from 'rxjs/BehaviorSubject'; | |
export interface AlertConfig { | |
description?: string; | |
okButtonLabel?: string; | |
cancelButtonLabel?: string; | |
okCallback?: Function; | |
displayLoading?: boolean; |
By: @BTroncone
Also check out my lesson @ngrx/store in 10 minutes on egghead.io!
Update: Non-middleware examples have been updated to ngrx/store v2. More coming soon!
Table of Contents
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft
, elem.offsetTop
, elem.offsetWidth
, elem.offsetHeight
, elem.offsetParent
/** | |
* @license CC0 1.0 (http://creativecommons.org/publicdomain/zero/1.0/) | |
* | |
* The problem: | |
* You need to make a cross-domain request for JSON data, but the remote | |
* server doesn't send the necessary CORS headers, and it only supports | |
* simple JSON-over-HTTP GET requests (no JSONP support). | |
* | |
* One possible solution: | |
* Use 'jsonp-proxy-request-interceptor' to proxy the request through |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.