52
edits
(idea for presentation and discussion added) |
(Add idea for presentation/discussion of potentially type checking JS) |
||
| Line 18: | Line 18: | ||
This presentation and discussion would cover my journey as a GSoC student and Thunderbird Intern. I will talk about the difficulties I faced and how university students and junior developers can start their contribution with Thunderbird. | This presentation and discussion would cover my journey as a GSoC student and Thunderbird Intern. I will talk about the difficulties I faced and how university students and junior developers can start their contribution with Thunderbird. | ||
== '''Why we might want to start type checking our JavaScript and how that could even work''' == | |||
Type: Presentation & Discussion | |||
Host/Speaker: [mailto:paul@thunderbird.net Paul Morris [:pmorris<nowiki>]</nowiki>] | |||
JavaScript is a dynamically typed language, but now [https://www.typescriptlang.org/ TypeScript]'s tooling can be used to statically [https://www.typescriptlang.org/docs/handbook/type-checking-javascript-files.html type check plain vanilla JavaScript files] (with some help from [https://jsdoc.app/ JSDoc]). Type checking offers various benefits that include catching certain classes of bugs sooner (before they get to users) and making code easier to understand. Tools like ESLint and Prettier have improved Thunderbird's JavaScript code and developer experience. Would type checking be a good next step and how might that work? | |||
edits