Could you please double check this logic ?

This change seems to trigger the following error:

class Base {
  constructor(t: Type) {...}
}

class Extend extends Base {
 // no ctor
}

// -> Can't resolve all parameters for BasicSearchResultChildComp: (?)

Will have a look

This looks weird, I can even confirm the OP's plunker works under 6.0.0-beta.5. Could you provide a little more information about:

• Whether the code compiled to es5 or es2015+?
• Does Base annotated with @Injectable()?
• Is Type a class rather than a interface or type?

What I can share for now:

---- controller.ts
// no annotation
export class Controller implements OnInit {
  @Input() result: ...;

  constructor(
      private readonly a: AType,
      private readonly g: GType) {}
// ...
}

---- comp.ts
@Component({
  selector: '...',
  templateUrl: ...,
})
export class Comp extends Controller {
}

I'll investigate more tomorrow

It could be the lacking of class decorator in base class caused this problem, but I guess that's by design?

I would rather call it a workaround. And IIRC it was working in some older versions without a decorator on an abstract base class.

That's due to lacking of inheritance support in some very old versions, the current behavior is the natural result of combining inheritance semantics and TypeScript metadata emitting rules.

If there's no way to fix (except changing the design), I think it can be called by design (but could be a design failure).

Also, this change only make the behavior consistent between compiled classes (functions) and native classes, previously the natives class doesn't follow inheritance semantics (cannot inherit parent parameters), so some errors are now revealed, not introduced (just better error message).

@trotyl @devoto13 thanks for your help - the issue was on our side !
I'll probably reapply the change soon.