I have a react-redux application written in typescript with immutable package. There I have a data, which comes from api and in store I pack it to Map. In all application they are used as a Map.
I created an interface:
export interface PaymentMethod extends Immutable.Map<string, string | NamedType<number>> {
id: string;
name: string;
description: string;
accountNr: string;
paymentMethodType: NamedType<number>;
}
In general it works very good. Except tests, where I create data this way:
const dummyPaymentMethod: PaymentMethod = Map({
id: '',
name: '',
description: '',
accountNr: '',
paymentMethodType: { id: 1, name: '' },
});
and then I get a lint error:
Error:(116, 13) TS2322:Type 'Map<string, string | { id: number; name: string; }>' is not assignable to type 'PaymentMethod'.
Property 'id' is missing in type 'Map<string, string | { id: number; name: string; }>'.
I feel totally lost, as I can see id in interface and in my dummy data.
I would appreciate some light on it. I feel that somehow I should pass the list of acceptable keys to my Map, but no idea, how to do this.
EDIT: misspell
We used it like this in our project (slightly different approach):
interface ImmutableMap<T> extends Map<string, any> {
get<K extends keyof T>(name: K): T[K];
}
We used an older version of the Immutable.js
typings that didn't used mapped types yet (T[K]
). AFAIK typings are updated since then and there is no need to overwrite the get
method.
EDIT: Actually the get
method still is not fully type safe unlike the above. So overwriting the method still has its merits.
With the above declaration you can then create immutable maps like:
type AuthState = ImmutableMap<{
user:string|null;
loggedIn:boolean;
}>;
const authState:AuthState = fromJS({ user: 'Alice', loggedIn: true });
Ideally, you would like typings like this:
/**
* Imaging these are typings for your favorite immutable
* library. We used it to enhance typings of `immutable.js`
* with the latest TypeScript features.
*/
declare function Immutable<T>(o: T): Immutable<T>;
interface Immutable<T> {
get<K extends keyof T>(name: K): T[K];
set<S>(o: S): Immutable<T & S>;
}
const alice = Immutable({ name: 'Alice', age: 29 });
alice.get('name'); // Ok, returns a `string`
alice.get('age'); // Ok, returns a `number`
alice.get('lastName'); // Error: Argument of type '"lastName"' is not assignable to parameter of type '"name" | "age"'.
const aliceSmith = alice.set({ lastName: 'Smith' });
aliceSmith.get('name'); // Ok, returns a `string`
aliceSmith.get('age'); // Ok, returns a `number`
aliceSmith.get('lastName'); // Ok, returns `string`
In order to achieve the above with Immutable.js
you can create a small helper function, whose only purpose is to "fix" typings:
import { fromJS } from 'immutable';
interface Immutable<T> {
get<K extends keyof T>(name: K): T[K];
set<S>(o: S): Immutable<T & S>;
}
function createImmutable<T extends object> (o:T) {
return fromJS(o) as Immutable<T>;
}
Note that I used fromJS
in the example. This will create a Map
as long as the passed input is an Object
. The benefit of using fromJS
over Map
is that the typings are easier to overwrite.
Side note: You might also want to look into Record
s.
来源:https://stackoverflow.com/questions/43607652/typescript-immutable-proper-way-of-extending-immutable-map-type