Generated TypeScript message class not compatible with generated message interface

[bhouser]

protobuf.js version: 6.8.0

Problem:
Message class instances cannot be assigned to interface typed variable (or function parameter);

Generated TypeScript definitions.

    interface IToken {
        message?: google.protobuf.IAny;
    }

    class Token {
        constructor(properties?: core.IToken);
        public message?: (google.protobuf.IAny|null);
        public static encode(message: core.IToken, writer?: $protobuf.Writer): $protobuf.Writer;
        public static encodeDelimited(message: core.IToken, writer?: $protobuf.Writer): $protobuf.Writer;
        public static decode(reader: ($protobuf.Reader|Uint8Array), length?: number): core.Token;
        public static decodeDelimited(reader: ($protobuf.Reader|Uint8Array)): core.Token;
        public static verify(message: { [k: string]: any }): (string|null);
    }

Code resulting in TypeScript Error:

const myEncodedToken = Token.encode(myToken);

TypeScript Error:

Error:(42, 37) TS2345:Argument of type 'Token' is not assignable to parameter of type 'IToken'.
  Types of property 'message' are incompatible.
    Type 'IAny | null | undefined' is not assignable to type 'IAny | undefined'.
      Type 'null' is not assignable to type 'IAny | undefined'.

A similar problem was fixed in response to this issue: #826. The types now correctly reflect that an instantiated message class can have undefined fields. But assignment to the interface (by calling Message.encode for example) is still impossible.

Example generated TypeScript interface which would fix the problem:

    interface IToken {
        message?: google.protobuf.IAny | null;
    }

[dcodeIO]

Does this issue still exist in master? There have been a couple merges that might, or might not, prevent this. Otherwise, do you have an updated example causing the issue?

[bhouser]

I haven't attempted with master. The earliest I'll be able to test it is Monday.

[mknapik]

I had the same issue in version 6.8.0. I've just upgraded to 6.8.1 and it seems it was fixed and type implements an interface.

[sherlock1982]

6.8.3 still the same issue.
In interface member is declared as (string|null|undefined) and in class it's string