function handleRelations<T extends Model>(modelClass: T) {
Look up Generics Constraints in the typescript manual.
2) That's not a Typecript question, that's an object-oriented question. The answer is "you can't, and shouldn't".
If I have an Animal[] and .map it to call a function on each return value... animals.map(a => a.idColumn().whatIsValidHere)
... then what is always safe for whatisvalidhere if it's sometimes a string sometimes an array sometimes an Invoice, etc.
3)
interface SimpleObject<T> {
[key: string] : T
}
is a bit more useful. Stick in /shared/ or wherever you keep such things.
You beat me to it! typeof Model and T extends Model are the useful features here, but I also agree with Edward Tam - you should probably eschew subclassing in general. "Is a" object relationships are the tightest form of coupling that exists. Instead use functions or even mixins, if you must attach "methods" to your objects. You probably don't need a base class when you have interfaces and mixins available to you.
1)
function handleRelations<T extends Model>(modelClass: T) {Look up Generics Constraints in the typescript manual.
2) That's not a Typecript question, that's an object-oriented question. The answer is "you can't, and shouldn't".
If I have an Animal[] and .map it to call a function on each return value...
animals.map(a => a.idColumn().whatIsValidHere)... then what is always safe for
whatisvalidhereif it's sometimes a string sometimes an array sometimes an Invoice, etc.3)
is a bit more useful. Stick in /shared/ or wherever you keep such things.
You beat me to it!
typeof ModelandT extends Modelare the useful features here, but I also agree with Edward Tam - you should probably eschew subclassing in general. "Is a" object relationships are the tightest form of coupling that exists. Instead use functions or even mixins, if you must attach "methods" to your objects. You probably don't need a base class when you have interfaces and mixins available to you.is ais strong, but can be loosened with Factories and Bridge PatternHaven't found a good use for the Bridge Pattern, but I've often wondered why more ORMs aren't using Factories/mixins