Warning: This page has not been updated in over over a year and may be outdated or deprecated.
community_call:minutes20230110
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
community_call:minutes20230110 [2023/01/10 14:00] – [VuFind® Community Call Minutes: January 10, 2023] demiankatz | community_call:minutes20230110 [2023/01/10 14:24] – [2. Technology Demo: Typescript Annotations] demiankatz | ||
---|---|---|---|
Line 46: | Line 46: | ||
* Prerequisite: | * Prerequisite: | ||
- | ==== 2. Technology Demo ==== | + | ==== 2. Technology Demo: Typescript Annotations |
+ | Chris mentioned that after reflecting on feedback from last month' | ||
+ | |||
+ | Chris then demonstrated a way to add [[https:// | ||
+ | |||
+ | It should be easy to integrate type checking into continuous integration. It should also be possible to enforce the inclusion of typing via eslint with " | ||
+ | |||
+ | We should be able to introduce this via a new pull request; no need to wait on other "npm scripts" | ||
+ | |||
+ | There was discussion of whether we should at some point introduce a compilation step for our Javascript assets. Down sides: introducing compilation steepens learning curve; could complicate deployment process for complex sites like Finna with many views. Advantage: would make it easier to manage dependencies, | ||
+ | |||
+ | Possible middle ground on compilation: | ||
==== 3. Open Q&A / Other Topics? ==== | ==== 3. Open Q&A / Other Topics? ==== | ||
community_call/minutes20230110.txt · Last modified: 2023/01/10 14:31 by demiankatz