mattdsteele / advent-of-code

Advent of Code

CI/CD Tooling

In the cmd/ folder are the following utilities:

setup/ - Preps a day by downloading the input

submit/ - Submits an answer

sync/ - Identifies any answers not submitted successfully, and submits each in turn

Automation

• Submits entries to AOC via https://github.com/mattdsteele/aoc-submit-action
• Stars via https://github.com/mattdsteele/aoc-stars-shield

advent-of-code's Issues

Bug: You only did the first one.

https://twitter.com/mattdsteele/status/938629743984959488

¯\_(シ)_/¯

Day setup boilerplate

• ✔️ Download and parse input
• 🕐 Make test file (from template)
• 🕐 Make prod file (from template)

Get feedback from Nick on TypeScript environment

Hey @nicknisi!

Just gonna open an issue here as I try figuring this stuff out, slightly higher fidelity than Twitter!

So! I've got a basic setup up & running in this repo.

I'm gonna write tests & production code in TypeScript.

My tools:

• Typescript 1.7.3
• tsc via tsconfig.json, typings through tsd.json; a postinstall hook runs tsd install
• Source code in src/, test in test/, JS compiiled into built/[src|test]
• Using neovim with typescript-vim plugin (no customizations)
• Mocha for tests
• npm scripts to actually run things; might add Grunt/Gulp later

My workflow right now is to run npm test, it has a hook to run tsc followed by mocha.

A few questions I've got about a TS env:

• Any useful way to speed things up? Right now npm test takes three seconds to do basically nothing; I feel like it could be faster.
• Are you compiling/getting feedback directly in vim? The typescript-vim plugin's docs say I can run :make, but I get this error:
  
• If you are getting feedback in neovim, any secrets to making it async?
• Is there a better way to handle the typings pragma? It's kind of a pain to have to type the /// <reference stuff
• Any other pain points I should be aware of, or stuff you wish was handled better?