From eae0112b1b590765e1809dc99586dc2345e5ba08 Mon Sep 17 00:00:00 2001 From: Eemeli Aro Date: Thu, 26 Apr 2018 08:09:33 +0300 Subject: [PATCH] feat(talk): Add Eemeli's second lighting talk (#20) --- src/schedules/25-04-2018.js | 1 + src/talks/eemeli-aro-2.js | 11 +++++++++++ src/talks/index.js | 1 + 3 files changed, 13 insertions(+) create mode 100644 src/talks/eemeli-aro-2.js diff --git a/src/schedules/25-04-2018.js b/src/schedules/25-04-2018.js index bae2684..bb2510a 100644 --- a/src/schedules/25-04-2018.js +++ b/src/schedules/25-04-2018.js @@ -83,6 +83,7 @@ module.exports = { }, require("../talks/andrey-okonetchnikov"), require("../talks/sven-sauleau"), + require("../talks/eemeli-aro-2"), ], }, { diff --git a/src/talks/eemeli-aro-2.js b/src/talks/eemeli-aro-2.js new file mode 100644 index 0000000..2d22198 --- /dev/null +++ b/src/talks/eemeli-aro-2.js @@ -0,0 +1,11 @@ +const enums = require("../enums"); +const keywords = require("../keywords"); +const speaker = require("../speakers/eemeli-aro"); + +module.exports = { + speakers: [speaker], + title: "Why I YAML", + description: "I'm writing my own YAML library, because none of the existing ones allowed me to manage comments within YAML files. Apparently this is not a thing one should do, as \"The YAML spec is larger than the XML and XML Namespaces specs combined\" and \"No one in their right mind would want to write a parser for it.\"\n\nBut, well, here we are. Let me explain where \"here\" is, the route I took, and why any of this matters.", + type: enums.LIGHTNING_TALK, + keywords: [keywords.TOOLING], +}; diff --git a/src/talks/index.js b/src/talks/index.js index 88437ee..0449250 100644 --- a/src/talks/index.js +++ b/src/talks/index.js @@ -2,6 +2,7 @@ module.exports = [ require("./christian-alfoni"), require("./david-khourshid"), require("./eemeli-aro"), + require("./eemeli-aro-2"), require("./gant-laborde"), require("./jani-evakallio"), require("./kasia-jastrzebska"),