Definition overriding only takes first definition

[bmalehorn]

For example,

declare class Foo {
  public y: {
    /**
     * foo
     * @returns The current y value.
     */
    (): number;
    /**
     * bar
     * @param value The desired y value.
     * @returns The calling Foo.
     */
    (value: number): Foo;
  }

  /**
   * baz
   * @returns The current z value.
   */
  public z(): number;
  /**
   * ack
   * @param value The desired z value.
   * @returns The calling Foo.
   */
  public z(value: number): Foo;
}

Will produce this:

Notice that z's documentation is messed up. Only the first docstring is taken.

Really, y and z should have identical documentation.

[sebastian-lenz]

Hi bmalehorn, nice to hear from you. Did you click on the second signature of z? It's actually an accordion and you can reveal the different overload definitions by selecting its signatures.

I don't know why you expect the reflection of y and z to be the same. y is an object literal while z is a function with multiple overloads.

[sebastian-lenz]

Now I see it, the two call signatures of y should be placed in an accordion too.

[Evgenus]

+1 for constructors in accordion

[bmalehorn]

Did you click on the second signature of z?

Ah, I can't believe I didn't notice this earlier. I'm fine with this setup.

You can change y to accordion if you want, but I don't think it's necessary. If you change y to accordion, it would suddenly change to non-accordion as soon as you added a non-function signature.

You can close this issue if you want, or keep it open if you want to make y accordion.