-
Notifications
You must be signed in to change notification settings - Fork 1
Feature/kak/update dependencies#187 #228
Feature/kak/update dependencies#187 #228
Conversation
Using `ncu -a`. Closes azavea#187.
Fix error on npm serve: `Cannot find module webpack/lib/node/NodeTemplatePlugin`.
For updated npm packages and added webpack.
Fixes error after package upgrade: `Cannot import type declaration files. Consider importing geojson instead of @types/geojson.`.
After package upgrade, errors on `ThresholdIndicatorQueryOpts` type extension. Sub-object no longer inherits properties and must now explicitly list them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
import { IndicatorQueryOpts } from './indicator-query-opts.model'; | ||
|
||
export interface ThresholdIndicatorQueryOpts extends IndicatorQueryOpts { | ||
params: { | ||
threshold: Number; | ||
threshold_units: string; | ||
threshold_comparator: string; | ||
|
||
// from base |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I originally did this as well after the TS2.4 upgrade, but then went further down the rabbit hole and refactored IndicatorQueryOpts such that IndicatorQueryOpts.params is now interface IndicatorParams
instead of any
, and can be extended by ThresholdIndicatorParams
. ThresholdIndicatorQueryOpts
disappears.
No action necessary here, just more of a heads up that a larger change related to this is coming in the PR for #212. It enforces type checking far better in a few places, and avoids the awkwardness of having to redefine parameters as is done here.
Linter now warns of shadowed variables.
Overview
Update npm dependencies, using
ncu -a
. Fixes some resulting server errors.Notes
Doing this task now in case the updates to the karma Chrome launcher might help in addressing some of the spurious Jenkins test run failures. If not, will try the
--no-sandbox
flag workaround described here.Testing Instructions
Closes #187.