(Full description and list of commands at - https://npmjs.org/doc/index.html)
Make sure to export your local $PATH and prepand relative ./node_modules/.bin/:
# Path to your oh-my-zsh configuration. | |
export ZSH=$HOME/.oh-my-zsh | |
# Set name of the theme to load. | |
# Look in ~/.oh-my-zsh/themes/ | |
# Optionally, if you set this to "random", it'll load a random theme each | |
# time that oh-my-zsh is loaded. | |
#export ZSH_THEME="robbyrussell" | |
export ZSH_THEME="zanshin" |
(Full description and list of commands at - https://npmjs.org/doc/index.html)
Make sure to export your local $PATH and prepand relative ./node_modules/.bin/:
Press minus + shift + s
and return
to chop/fold long lines!
(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.
var React = require('react/addons'); | |
var Table = require('./table.jsx'); | |
var rows = [ | |
{ | |
'id' : 1, | |
'foo': 'bar' | |
}, | |
{ | |
'id' : 2, | |
'foo': 'baarrrr' |
Hi Nicholas,
I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:
The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't
public interface StoreRepository extends PagingAndSortingRepository<Store, String>, | |
QueryDslPredicateExecutor<Store>, QuerydslBinderCustomizer<QStore> { | |
@RestResource(rel = "by-location") | |
Page<Store> findByAddressLocationNear(Point location, Distance distance, Pageable pageable); | |
default void customize(QuerydslBindings bindings, QStore store) { | |
bindings.bind(store.address.city).single((path, value) -> path.startsWith(value)); | |
bindings.bind(String.class).single((StringPath path, String value) -> path.contains(value)); | |
} |
@Configuration | |
public class SnakeCaseApplicationConfiguration { | |
@Bean | |
public OncePerRequestFilter snakeCaseConverterFilter() { | |
return new OncePerRequestFilter() { | |
@Override | |
protected void doFilterInternal(HttpServletRequest request, HttpServletResponse response, FilterChain filterChain) throws ServletException, IOException { | |
final Map<String, String[]> parameters = new ConcurrentHashMap<>(); | |
for (String param : request.getParameterMap().keySet()) { |
Options included below:
docker-compose
brew
This gist was originally created for Homebrew before the rise of Docker, yet it may be best to avoid installing mysql via brew
any longer. Instead consider adding a barebones docker-compose.yml
for each project and run docker-compose up
to start each project's mysql service.