In August 2007 a hacker found a way to expose the PHP source code on facebook.com. He retrieved two files and then emailed them to me, and I wrote about the issue:
http://techcrunch.com/2007/08/11/facebook-source-code-leaked/
It became a big deal:
http://www.techmeme.com/070812/p1#a070812p1
The two files are index.php (the homepage) and search.php (the search page)
| // By Simon Lydell 2015. | |
| // This file is in the public domain. | |
| var stdin = require("get-stdin") | |
| var tools = require("text-frequencies-analysis") | |
| var helpers = require("text-frequencies-analysis/lib/helpers") | |
| stdin(function(text) { | |
| process.stdout.write(tools.jsonStringifyRow(convert(JSON.parse(text)))) | |
| }) |
| /* | |
| Example of how to get raw mouse input data using the native Windows API | |
| through a "message-only" window that outputs to an allocated console window. | |
| Not prepared for Unicode. | |
| I don't recommend copy/pasting this, understand it before integrating it. | |
| */ | |
| // Make Windows.h slightly less of a headache. | |
| #define NOMINMAX |
All libraries have subtle rules that you have to follow for them to work well. Often these are implied and undocumented rules that you have to learn as you go. This is an attempt to document the rules of React renders. Ideally a type system could enforce it.
A number of methods in React are assumed to be "pure".
On classes that's the constructor, getDerivedStateFromProps, shouldComponentUpdate and render.
Credit Circle People for old skins
See how a minor change to your commit message style can make a difference.
Tip
Have a look at git-conventional-commits , a CLI util to ensure these conventions and generate verion and changelogs
Composition of <Route> elements in React Router is changing in v6 from how it worked in v4/5 and in Reach Router. React Router v6 is the successor of both React Router v5 and Reach Router.
This document explains our rationale for making the change as well as a pattern you will want to avoid in v6 and a note on how you can start preparing your v5 app for v6 today.
In React Router v5, we had an example of how you could create a element](https://github.com/remix-run/react-router/blob/320be7afe44249d5c025659bc00c3276a19f0af9/packages/react-router-dom/examples/Auth.js#L50-L52) to restrict access to certain routes on the page. This element was a simple [wrapper around an actual element that made a simple decision: is the user authenticated or not? If so, ren
