`@deprecated` nested namespace handling is buggy about typescript HOT 2 OPEN

I would love to see some clarification on what you guys think is the correct behaviour so that we can follow-suit!

I have no idea and I don't think it's likely that a poll of developers would produce a strong majority outcome either. It seems much more clarifying to either write

/** @deprecated */
namespace Foo1 {
  export namespace Bar {
    export const x = 1;
  }
}

or

namespace Foo1 {
  /** @deprecated */
  export namespace Bar {
    export const x = 1;
  }
}

depending on which is intended (hopefully they both work more consistently?)

A PR to make them consistent would be fine.

from typescript.

Yeah I wasn't sure what the "correct" behaviour should be and I don't think there's a right answer either.

The thing I think that is missing right now is that the order of declarations matters for TS to do its strike through.

I think it'll be worth linting and enforcing against the ambiguity in DefinitelyTyped. I'll raise an issue over there.

from typescript.