Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
(bug) HttpOptions.headers:HttpHeaders compatibility issue with aot compilation
See original GitHub issueRunning
$ ng build --prod
while the module is injected to the app.
We get the following error
ERROR in app/app.module.ts(14,21): Error during template compile of 'AppModule' Function calls are not supported in decorators but 'HttpHeaders' was called.
This might be due to the fact that simple assignments are only allowed during module declarations.
and we’re trying to pass new HttpHeaders(...header String/objects) into the module declaration.
Possible Solution:
- Add a new optional config headersConfig into HttpOptions, which will be the input signature of HttpHeaders() constructor
- Make it working with this way as well.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
After some tests, it would be best if the options we provide for
paramsandheaderswill be{[key: string]: string}object and not constructed class.It will require to change some types and interfaces but it should be able to do it without breaking the outer API. I’ll cover that in PR soon.
the fix should be in master now, @resistancecanyon please try the latest version and see if there is everything resolved.