From 0789e761a5570c7668805fd699dddff13d093174 Mon Sep 17 00:00:00 2001 From: hasezoey Date: Fri, 20 Sep 2019 22:04:22 +0200 Subject: [PATCH] Cleint -> Client --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index f9d24f9..9a00027 100644 --- a/README.md +++ b/README.md @@ -160,9 +160,9 @@ import { use, delegate } from "typescript-mix" Consider the following piece of code. ![alt text](https://github.com/michaelolof/typescript-mix/blob/master/imgs/2018-05-30%2021_32_46-Preview%20README.md%20-%20typescript-mix%20-%20Visual%20Studio%20Code.png?raw=true) -Cleint One uses two mixins that contain the same method mixIt(). How do we resolve this? Which method gets picked?. +Client One uses two mixins that contain the same method mixIt(). How do we resolve this? Which method gets picked?. One advantage of extending interfaces as we've defined above is that we're essentially telling TypeScript to mix-in the two mixin interfaces into the ClientOne interface. So how does TypeScript resolve this? ![alt text](https://github.com/michaelolof/typescript-mix/blob/master/imgs/2018-05-30%2021_49_13-final.ts%20-%20typescript-mix%20-%20Visual%20Studio%20Code.png?raw=true) -Notice that TypeScript's intellisense calls MixinOne.mixIt() method. Therefore to be consistent with TypeScript and avoid confusion the '@use' decorator also implements MixinOne.mixIt() method. \ No newline at end of file +Notice that TypeScript's intellisense calls MixinOne.mixIt() method. Therefore to be consistent with TypeScript and avoid confusion the '@use' decorator also implements MixinOne.mixIt() method.