| { | |
| "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.
This is a work in progress. Please don't take this as something that will definitely happen, we all know what happens to well laid plans and I need to present it to the rest of the TypeScript team in order to figure out a lot of feasibility questions.
The examples in this PR assumes [CLI DX] Improve positioning of compiler error messaging info #45717 is merged
In 4.4, all diagnostic messages from TypeScript are treated the same, we have a massive .JSON file of ±2000 diagnostic messages which are used everywhere from compiler messages to CLI help. Aside from some simple string manipulation, these are effectively what we output for all error messages. I'd like to propose that we break this pattern, just for error TS2322.
TS2322 is our 'type x is not assignable to y' error, you'd see it for const str: string = 123 and I expect it is the most seen
| [229,"collections" | |
| [237,"json3" | |
| [240,"intl" | |
| [242,"ofe" | |
| [245,"rickshaw" | |
| [246,"webcrypto" | |
| [249,"tsc-watch" | |
| [253,"slackdown" | |
| [256,"node-os-utils" | |
| [256,"touch-events" |
| name: Upload infra | |
| on: | |
| push: | |
| branches: | |
| - main | |
| - prod | |
| jobs: | |
| build-and-deploy: |
| ❯ tree packages/typescriptlang-org/public -P "*.html" | |
| packages/typescriptlang-org/public | |
| ├── Handbook | |
| │ └── index.html | |
| ├── License.html | |
| ├── Playground | |
| │ └── index.html | |
| ├── Tutorial | |
| │ └── index.html |