| 更新: | 2013-11-01 |
|---|---|
| バージョン: | 0.0.1 |
| 作者: | @voluntas |
| URL: | http://voluntas.github.io/ |
概要
| 更新: | 2013-11-01 |
|---|---|
| バージョン: | 0.0.1 |
| 作者: | @voluntas |
| URL: | http://voluntas.github.io/ |
概要
| #!/usr/bin/env ruby | |
| require 'xcodeproj' | |
| require 'fileutils' | |
| PROJECT = 'Unity-iPhone' | |
| TARGET = 'Unity-iPhone' | |
| LIBRARY = 'Libraries' | |
| LOCALIZE = 'Localize' |
| function permutations(array, r) { | |
| // Algorythm copied from Python `itertools.permutations`. | |
| var n = array.length; | |
| if (r === undefined) { | |
| r = n; | |
| } | |
| if (r > n) { | |
| return; | |
| } | |
| var indices = []; |
I've been converting the web client part of an application I'm developing for a client from plain old JavaScript to React and Flux. (Because this is closed-source client work, I will be a bit vague about what the application is and does.)
Something about my data, my use case, and how I've implemented things, or some combination of those three, doesn't fit the Flux pattern well. So I am writing this to explain my problem and hopefully get some interesting feedback on it. (If you're reading this: thanks.)
I have a Python server which talks to a PostgreSQL database and provides data in JSON format over a REST-ish API (not pure REST, more RPC-style).
facebook/flux 2.0.32.1.0で追加されたflux/utilsについて
see also 2015-08-17のJS: redux 1.0.0、flux-utils、Firefox 40 - JSer.info
はてなブックマーク検索を作りながらFlux Utilsについて学ぶ | Web Scratchにもっと具体的な解説を書きました
Variadic functions, such as the common zip function on arrays, are convenient and remove the need for lots of specific arity-function variants, e.g., zip2, zip3, zip4, etc. However, they can be difficult and tedious to type correctly in TypeScript when the return type depends on the parameter types, and the parameter types are heterogeneous.
Given a typical zip on arrays:
const a: number[] = [1, 2, 3]| const { withDangerousMod, withPlugins } = require("@expo/config-plugins"); | |
| const { | |
| mergeContents, | |
| } = require("@expo/config-plugins/build/utils/generateCode"); | |
| const fs = require("fs"); | |
| const path = require("path"); | |
| async function readFileAsync(path) { | |
| return fs.promises.readFile(path, "utf8"); | |
| } |
| name | prd |
|---|---|
| description | Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out. |
Create detailed Product Requirements Documents that are clear, actionable, and suitable for autonomous AI implementation via the Ralph loop.