Decorator usages no longer working with AOT when a function is passed as a parameter

I’m submitting a…

[x] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

Given the following decorator:

export function foo(
  test: any
) {
  return (_target: any, _name: string, descriptor: PropertyDescriptor) => {
  };
}

And the following usage:

@foo(() => 5)
bar() {
}

I am getting the following error:

Error encountered in metadata generated for exported symbol 'xxx':
 C:/git/xxx/_artifact/xxx/xxx.ts:48:24: Metadata collected contains an error that will be reported at runtime: Lambda not supported.
  {"__symbolic":"error","message":"Lambda not supported","line":47,"character":23}

Changing the decorator usage to the following works:

@foo(5)
bar() {
}

This breaks when building AOT

Expected behavior

Function parameters in decorators worked before and are expected to work in 5.x.x

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

This functionality used to work correctly in 4.x.x

Environment

Angular version: 5.1.1


Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
 
For Tooling issues:
- Node version: 8.7.0 
- Platform:  Windows 

Others:

[chuckjaz]

@alan-agius4 I am writing the documentation for "strictMetadataEmit" today and it will land as part of my work on #20987.

In this case you can add

// @dynamic
export function foo(
  test: any
) {
  return (_target: any, _name: string, descriptor: PropertyDescriptor) => {
  };
}

Alternately, you can just not enable "strictMetadataEmit" which is off by default. Unless you are bundling a library for npm, you should not use this option.

I am closing this as this is working as intended and Angular 4 didn’t support this either and would emit the same error if you did not specify that the function was not intended to be used in an Angular annotation.

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}