Suppose you're opening an issue and there's a lot noisey logs that may be useful.
Rather than wrecking readability, wrap it in a <details> tag!
<details>
Summary Goes Here| { | |
| "hosting": { | |
| "public": "public", | |
| "rewrites": [ | |
| { | |
| "source": "**", | |
| "function": "app" | |
| } | |
| ], | |
| "redirects": [{ |
| const functions = require("firebase-functions") | |
| const cors = require("cors") | |
| const express = require("express") | |
| /* Express with CORS & automatic trailing '/' solution */ | |
| const app3 = express() | |
| app3.use(cors({ origin: true })) | |
| app3.get("*", (request, response) => { | |
| response.send( | |
| "Hello from Express on Firebase with CORS! No trailing '/' required!" |
| var gulp = require('gulp'); | |
| var sourcemaps = require('gulp-sourcemaps'); | |
| var source = require('vinyl-source-stream'); | |
| var buffer = require('vinyl-buffer'); | |
| var browserify = require('browserify'); | |
| var watchify = require('watchify'); | |
| var babel = require('babelify'); | |
| function compile(watch) { | |
| var bundler = watchify(browserify('./src/index.js', { debug: true }).transform(babel)); |
| # 原則として開く用語。修正前→修正後 | |
| 敢えて→あえて | |
| 当たって→あたって | |
| 余り→あまり | |
| 予め→あらかじめ | |
| 有り→あり | |
| 或いは→あるいは | |
| 如何→いかが | |
| 幾つか→いくつか | |
| 致し→いたし |
Hello, visitors! If you want an updated version of this styleguide in repo form with tons of real-life examples… check out Trellisheets! https://github.com/trello/trellisheets
“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”
You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?
| // Amazonの注文履歴をTSV形式で出力するスクリプト | |
| // | |
| // 2015-01-01 時点での DOM 構造に対応, GoogleCrome, Opera でテスト済。 | |
| // formatEntry関数を書き換えれば自由な書式で出力できます。 | |
| // | |
| // 参考: | |
| // - Amazonの注文履歴をCSV形式にして出力するスクリプト | |
| // https://gist.github.com/arcatdmz/8500521 | |
| // - Amazon で使った金額の合計を出す奴 (2014 年バージョン) | |
| // https://gist.github.com/polamjag/866a8af775c44b3c1a6d |
この記事はFrontrend Advent Calendar 2014 - Qiita 10日目の記事です。
プログレッシブ・エンハンスメントは単にJavaScriptをオフにしているユーザのサポートをするか、否かという意味ではありません。
(ちなみに、Gov.ukによると1.1%のユーザはJavaScriptを利用していない、もしくは利用できないという調査結果となっています)
もちろん、古いブラウザに対するアプローチだけでもありません。
デスクトップ、ラップトップ、スマートフォンやタブレット、そしてスマートウォッチなど、今では多くのデバイスにブラウザが搭載されています。
The idea is based on a gist by @jimbojsb.
You can use Pygments or Highlight.
brew install python