| <?php | |
| trait CastsValueObjects | |
| { | |
| protected function castAttribute($key, $value) | |
| { | |
| $castToClass = $this->getValueObjectCastType($key); | |
| // no Value Object? simply pass this up to the parent | |
| if (!$castToClass) { | |
| return parent::castAttribute($key, $value); |
| /* | |
| Extracts each .spa file in Spotify's Apps directory without manually doing it yourself. | |
| The default folder is put on the desktop. | |
| To change that, change the following part of the command: | |
| `~/Desktop/Apps && cd ~/Desktop/Apps` | |
| Procedure: | |
| 1. Change directory to /Applications/Spotify.app/Contents/Resources/Apps | |
| 2. Copy the files within the directory to ~/Desktop/Apps and change directory |
| /* | |
| Repacks the Spotify modules | |
| It converts your folder into a .spa file. (e.g., profile -> profile.spa) | |
| All module folders will be deleted after running this. | |
| As a result, the root directory will only contain .spa files. (ready to be placed into Spotify's contents) | |
| To run, simply `cd` into the root Apps folder of your skin. | |
| Then, take said folder and replace it with Spotify's Apps directory found at `/Applications/Spotify.app/Contents/Resources/Apps` | |
| #EXTM3U | |
| #EXTINF:-1 tvg-logo="https://listaiptvbrasil.com/images/seuiptv.png" group-title="", Listaiptvbrasil.com 17/07/17 | |
| http://sendvid.com/bn081x1f.mp4 | |
| #EXTINF:-1 tvg-logo="https://listaiptvbrasil.com/logo/globo.png" group-title="CANAL ABERTO",Globo Nordeste | |
| http://tv.ec.cx:1935/redecanais-stream-bobo/myStream/chunklist.m3u8 | |
| #EXTINF:-1 tvg-logo="https://listaiptvbrasil.com/logo/globo.png" group-title="CANAL ABERTO",Globo Rio | |
| http://95.141.32.136:8081/look/globox/playlist.m3u8 |
| (function(console) { | |
| console.saveImg = function(selector) { | |
| var imagesArray = selector || document.querySelectorAll('img'); | |
| var imagesObjArray = []; | |
| // Build img data object | |
| for (var i = 0; i < imagesArray.length; i++) { | |
| if ( imagesArray[i].getAttribute('src') !== null ) { |
| // We're going to create our own pipe function! | |
| // Some basic functions for easily understand the pipe function. | |
| // We'll combine those three function and send the value 4 to it. | |
| // Getting result of - 'The numner is: 10' | |
| const add1 = x => x + 1; | |
| const mul2 = x => x * 2; | |
| const title = x => `The number is: ${x}`; | |
| // @flow | |
| import React, { Component } from 'react'; | |
| import isSnapshot from '../../utils/isSnapshot'; | |
| export default function createDynamicComponent( | |
| importComponent: () => {default: any}, | |
| requireComponent: () => {default: any}, | |
| ) { | |
| type Props = { | |
| [name: string]: any, |
In this gist we are going to learn about basic goodies that we get from the library lodash/fp (fp stands for functional programming, great for ensuring immutability).We'll learn just by doing (step by step guided sample + codepens).
We'll cover lodash set and flow functions
tl;dr I built a demo illustrating what it might look like to add async rendering to Facebook's commenting interface, while ensuring it appears on the screen simultaneous to the server-rendered story.
A key benefit of async rendering is that large updates don't block the main thread; instead, the work is spread out and performed during idle periods using cooperative scheduling.
But once you make something async, you introduce the possibility that things may appear on the screen at separate times. Especially when you're dealing with multiple UI frameworks, as is often the case at Facebook.
How do we solve this with React?
| function ImgurDir { | |
| if [ -d ~/imgur\ albums ] | |
| then | |
| cd ~/imgur\ albums | |
| else | |
| mkdir ~/imgur\ albums | |
| cd ~/imgur\ albums | |
| fi | |
| } | |
| function readAlbum { |
