Combine default parameters and destructuring for a compact version of the defaults / overrides pattern.
function foo ({
bar = 'no',
baz = 'works!'
} = {}) {
This is a proof of concept which allows you to replay system events in a random order each time to make sure your UI can tolerate variable states.
I'm not sure if this is worthy of its on open source project with additional features like changing play back time, whitelisting/blacklisting actions etc but figured I'd put this out there to see if it piques anyones interest.
See a video of this in action here: [https://www.youtube.com/watch?v=wkoukONfwmA](Video on YouTube).
import { combineReducers } from 'redux'; | |
import users from './reducers/users'; | |
import posts from './reducers/posts'; | |
export default function createReducer(asyncReducers) { | |
return combineReducers({ | |
users, | |
posts, | |
...asyncReducers | |
}); |
import React from "react"; | |
import { render } from "react-dom"; | |
const ParentComponent = React.createClass({ | |
getDefaultProps: function() { | |
console.log("ParentComponent - getDefaultProps"); | |
}, | |
getInitialState: function() { | |
console.log("ParentComponent - getInitialState"); | |
return { text: "" }; |
import { Component } from 'react' | |
import { createStore, combineReducers } from 'redux' | |
import parseLinkHeader from 'parse-link-header' | |
const START = 'start' | |
const SUCCEED = 'succeed' | |
const ERROR = 'error' | |
const inflight = (state={}, action) => ( | |
((state) => ( |
Years ago, some smart folks that worked on JS engines realized that not all JS that's loaded into a page/app initially is needed right away. They implemented JIT to optimize this situation.
JIT means Just-In-Time, which means essentially that the engine can defer processing (parsing, compiling) certain parts of a JS program until a later time, for example when the function in question is actually needed. This deferral means the engine is freer to spend the important cycles right now on the code that's going to run right now. This is a really good thing for JS performance.
Some time later, some JS engine devs realized that they needed to get some hints from the code as to which functions would run right away, and which ones wouldn't. In technical speak, these hints are called heuristics.
So they realized that one very common pattern for knowing that a function was going to run right away is if the first character before the function
keyword was a (
, because that usually m
.composite-title, .composite-title, .vs-dark .monaco-workbench>.activitybar>.content { | |
background-color: rgba(40, 44, 52, 1) !important; | |
} | |
.tabs-container, .tab, .tab.active, .title-actions, .tablist, .tabs-container, .tabs, .composite.title { | |
background-color: rgba(40, 44, 52, 1) !important; | |
} | |
.tab.active, .tab { | |
border-right: 0px !important; |
Go here, select "View Bug Reporter", login, select "New", select "Bug Reporter".
UI/Usability
Always
App Store Review Guidelines should use different language when discouraging unqualified submissions to the app store
The proposal you’re about to read is not just a proposal. We have a working implementation of almost everything we discussed here. We encourage you to checkout and build our branch: our fork, with the relevant branch selected. Building and using the implementation will give you a better understanding of what using it as a developer is like.
Our implementation ended up differing from the proposal on some minor points. As our last action item before making a PR, we’re writing documentation on what we did. While I loathe pointing to tests in lieu of documentation, they will be helpful until we complete writing docs: the unit tests.
This repo also contains a bundled version of npm that has a new command, asset
. You can read the documentation for and goals of that comma