See also:
The bash has three default file descriptors for each process:
export const CACHE_STALE_AT_HEADER = 'x-edge-cache-stale-at'; | |
export const CACHE_STATUS_HEADER = 'x-edge-cache-status'; | |
export const CACHE_CONTROL_HEADER = 'Cache-Control'; | |
export const CLIENT_CACHE_CONTROL_HEADER = 'x-client-cache-control'; | |
export const ORIGIN_CACHE_CONTROL_HEADER = 'x-edge-origin-cache-control'; | |
enum CacheStatus { | |
HIT = 'HIT', | |
MISS = 'MISS', | |
REVALIDATING = 'REVALIDATING', |
See also:
The bash has three default file descriptors for each process:
In order of first appearance in The Morning Paper.
This is a proposal for ReactiveConf 2017 open call for Lightning talks. If you'd like to make this talk happen, please 🌟 this gist and retweet my tweet. 🙏
✅ Don't just prototype but code as a designer
This is a CFP for ReactiveConf open call for lightning talks. If you'd like to see this talk become a reality, please ⭐️ star this gist. #ReactiveConf
This proposal is not longer active. Context: https://twitter.com/siddharthkp/status/909818777314902016
Please 🌟 this gist to vote for this proposal!
No other topic in software development probably has so much controversy as linting.
With a wrong workflow linting can be really a pain and will slow you and your team down. With a proper setup, though, it can save you hours of manual work reformatting the code and reducing the code-review overhead.
// All webpack chunks have an identifier that is written to both the chunk and | |
// the chunk manifest. | |
// | |
// By default, webpack uses "int" identifiers, where the identifiers are | |
// sequentially generated after chunks are ordered by OccurenceOrderPlugin. | |
// | |
// The result of this is that small code changes may cause chunks to be | |
// reordered, leading to a cascading change of chunk ids, and a large number of | |
// chunk rehashes that could have been avoided. | |
// |
So migrating my existing app wasn't as troublesome as I originally thought. First thing I did was take a look at my router and routes
and figure try to make a mental model of all the files where I had nested routes in the existing app because those components/containers will contain {this.props.children}
. So I need to replace those with the nested <Match />
components.
So just to give an example:
<Router history={history}>
<Route path="/" component={App}>