You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example: SakuraApiModel and SakuraApiRoutable. Currently, SakuraApi is using abstract classes to define the static and prototype methods that are added to a class through injection via decorators like @Model and @Routable.
More recently, this has become a problem with upgrading to TypeScript 2.6 -- there appear to be stricter checks in place that's leading to some unit tests failing because of TypeScript typing errors.
Goal:
Explore possible mixin / abstract class alternatives
Implement those alternatives
Update all the npm dependencies
Note: This means that v0.8.0 will be a breaking update.
For example:
SakuraApiModel
andSakuraApiRoutable
. Currently, SakuraApi is using abstract classes to define the static and prototype methods that are added to a class through injection via decorators like@Model
and@Routable
.There are all kinds of problems with this:
{ new(...args: any[]): T }
parameter doesn't work for abstract classes microsoft/TypeScript#5843this
in function inputs/outputs microsoft/TypeScript#285More recently, this has become a problem with upgrading to TypeScript 2.6 -- there appear to be stricter checks in place that's leading to some unit tests failing because of TypeScript typing errors.
Goal:
Note: This means that v0.8.0 will be a breaking update.
Done - except for:
The Jasmine typedef has issues... Mongo upgrade is being tracked by #112
The text was updated successfully, but these errors were encountered: