While this gist has been shared and followed for years, I regret not giving more background. It was originally a gist for the engineering org I was in, not a "general suggestion" for any React app.
Typically I avoid folders altogether. Heck, I even avoid new files. If I can build an app with one 2000 line file I will. New files and folders are a pain.
2015/01/15時点の情報です。
v0.1.3が計画されてるけど、initial releaseのv0.1.0からはbugfixや細かな修正がほとんどで、大きな進化はしてない。 コミットもあまり活発ではない。 もしかしたら、Facebook社内でprivateブランチを育てていてまとまったところで出してくるのかも。 （JS等に比べて）開発者人口の少ないOCaml実装というのも、プルリクが集まりにくくOSS的な加速的進化が起きにくい原因かもしれない。
| var path = require('path'); | |
| var fs = require('fs'); | |
| var os = require('os'); | |
| var express = require('express'); | |
| var app = express(); | |
| var Busboy = require('busboy'); | |
| app.get('/', function (req, res) { | |
| res.send('<html><head></head><body>\ | |
| <form method="POST" enctype="multipart/form-data">\ |
| export default {} |
この記事はFrontrend Advent Calendar 2014 - Qiita 10日目の記事です。
プログレッシブ・エンハンスメントは単にJavaScriptをオフにしているユーザのサポートをするか、否かという意味ではありません。
(ちなみに、Gov.ukによると1.1%のユーザはJavaScriptを利用していない、もしくは利用できないという調査結果となっています)
もちろん、古いブラウザに対するアプローチだけでもありません。
デスクトップ、ラップトップ、スマートフォンやタブレット、そしてスマートウォッチなど、今では多くのデバイスにブラウザが搭載されています。
| // Safari, in Private Browsing Mode, looks like it supports localStorage but all calls to setItem | |
| // throw QuotaExceededError. We're going to detect this and just silently drop any calls to setItem | |
| // to avoid the entire page breaking, without having to do a check at each usage of Storage. | |
| if (typeof localStorage === 'object') { | |
| try { | |
| localStorage.setItem('localStorage', 1); | |
| localStorage.removeItem('localStorage'); | |
| } catch (e) { | |
| Storage.prototype._setItem = Storage.prototype.setItem; | |
| Storage.prototype.setItem = function() {}; |
| package main | |
| import ( | |
| "encoding/csv" | |
| "fmt" | |
| "net/http" | |
| ) | |
| func readCSVFromUrl(url string) ([][]string, error) { | |
| resp, err := http.Get(url) |
If you've reached this page, it's probably because your "parent-based and owner-based contexts differ".
As we've been iterating on React's "context" feature, we've discovered that the parent-based relationship is more useful than the owner-based relationship, so we're migrating to use a parent-based hierarchy.
In short, the owner of a component is whomever creates the component, while the parent of a component is whomever would be the containing ancestor in the DOM hierarchy. To learn more about the owner relationship, see the docs here: http://facebook.github.io/react/docs/multiple-components.html
In many cases, the owner and the parent are the same node, in which case, no further action is necessary.
| var mediaJSON = { "categories" : [ { "name" : "Movies", | |
| "videos" : [ | |
| { "description" : "Big Buck Bunny tells the story of a giant rabbit with a heart bigger than himself. When one sunny day three rodents rudely harass him, something snaps... and the rabbit ain't no bunny anymore! In the typical cartoon tradition he prepares the nasty rodents a comical revenge.\n\nLicensed under the Creative Commons Attribution license\nhttp://www.bigbuckbunny.org", | |
| "sources" : [ "http://commondatastorage.googleapis.com/gtv-videos-bucket/sample/BigBuckBunny.mp4" ], | |
| "subtitle" : "By Blender Foundation", | |
| "thumb" : "images/BigBuckBunny.jpg", | |
| "title" : "Big Buck Bunny" | |
| }, | |
| { "description" : "The first Blender Open Movie from 2006", | |
| "sources" : [ "http://commondatastorage.googleapis.com/gtv-videos-bucket/sample/ElephantsDream.mp4" ], |
