| { | |
| "keytrace": "kt-506c97fe5daa5227", | |
| "did": "did:plc:t732otzqvkch7zz5d37537ry" | |
| } |
| { | |
| "keytrace": "kt-4b94f5d55d9b6208", | |
| "did": "did:plc:t732otzqvkch7zz5d37537ry" | |
| } |
| { | |
| "lexicon": 1, | |
| "id": "com.puzzmo.puzzle", | |
| "defs": { | |
| "main": { | |
| "type": "record", | |
| "description": "A puzzle record.", | |
| "key": "tid", | |
| "record": { | |
| "type": "object", |
| import JavaScriptCore | |
| extension JSContext { | |
| subscript(key: String) -> Any { | |
| get { | |
| return self.objectForKeyedSubscript(key) | |
| } | |
| set{ | |
| self.setObject(newValue, forKeyedSubscript: key as NSCopying & NSObjectProtocol) | |
| } |
| // @ts-check | |
| const { join } = require("path") | |
| const { readFileSync, existsSync, readdirSync } = require("fs") | |
| /** @type {Map<string, import("../../.turbo/runs/2qS2rsViUIxwnKR9LWUL64tqpCP.json")>} */ | |
| const runs = new Map() | |
| const root = process.cwd() | |
| if (existsSync(join(root, ".turbo/runs"))) { |
| { | |
| "wordbind": { | |
| "hints": 0, | |
| "par": -2, | |
| "wordsFound": 8, | |
| "bestWord": 19, | |
| "bestWordText": "CORRIES", | |
| "timeToBestWord": 40022 | |
| }, | |
| "cubeclear": { |
To make sure I am explicit on the fragments (I know you, Jan, know this, but bypassers will read too) in GraphQL + Relay you can write a React DOM like
query root
- fragment A
- fragment B
- fragment C
and the query gets compiled by relay to make a single request, and then each fragment only gets the data it requested (even though it was part of a larger query of data)
| import "CoreLibs/sprites" | |
| import "CoreLibs/graphics" | |
| playdate.display.setRefreshRate(20) | |
| local gfx = playdate.graphics | |
| local spritelib = gfx.sprite | |
| local screenWidth = playdate.display.getWidth() | |
| local screenHeight = playdate.display.getHeight() |
| export type ABC = { | |
| one: 123 | |
| } |
Welcome to TypeScript's first ever set of virtual code challenges: Type | Treat (or "Type or Treat")! We will be presenting some "spooky" code challenges that will allow you to get deeper into the TypeScript language but in a fun way.
Starting tomorrow, a new code challenge will be posted every weekday, along with its solution the day after. The last solution will be posted on Halloween day.
Absolutely not! We want all developers, familiar with TypeScript or not to be apart of Type | Treat. Every day will have two different types of challenges, one for beginners/learners and one for intermediate/advanced developers. That way everyone can participate.