export 'IMetadata' was not found in 'kaop-ts'
See original GitHub issueHi,
I am facing this error with Angular 4.
export ‘IMetadata’ was not found in ‘kaop-ts’
import { Injectable } from '@angular/core'
import { AdvicePool, adviceMetadata, IMetadata } from 'kaop-ts'
@Injectable()
export class LogAspect extends AdvicePool {
static log(@adviceMetadata meta: IMetadata) {
console.log('Called: ', meta.target)
console.log('Args: ', meta.args)
}
}
Issue Analytics
- State:
- Created 6 years ago
- Comments:13 (11 by maintainers)
Top Results From Across the Web
How to find and use Kahoot! reports
Download report by clicking the three vertical dots next to Report options. Print report by clicking the three vertical dots next to Report ......
Read more >Key not found in metadata when exporting with PyCAP #62
I am exporting data from one of my REDCap projects. On the statement: project = Project(URL, TOKEN), I get a message "Exporting metadata...
Read more >Export Kahoot to any platform like Quizizz, Blooket or Gimkit
Go to your Kahoot Library and identify which Kahoot quiz you want to export. The Library tab can be found at the top...
Read more >export kahoot to google form
Speech and Hearing Kahoot Game » + Google Calendar + iCal Export. ... also include survey metadata (e.g. The form will be generated...
Read more >Features Comparison Between Poll Everywhere and Other ...
POLL EVERYWHERE ARCHIP...
Devices Required Any device that has internet connection access. Any dev...
PowerPoint Integration YES NO
Allowing Students to Ask Question YES, use Q&A...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks to @musti2! We learnt something new today
@k1r0s I think it was too early to close, since we didn’t provide a final solution.
I’ve been investigating. As you could have seen in angular/angular-cli#2034 (comment), the issue have implications on Webpack, TypeScript and Angular, so prob the issue will remain for a time, and is not in our side. Is not too important anyway since is a warning.
Anyway, I’ve tried several things from
kaop-ts
side, and there is nothing we can do. The best workaround I found is in the angular app re-exporting the interface from an inteface-only file (very important, don’t mix interfaces with variables, const, classes or functions in that file):That will remove the warnings.
@k1r0s I’d suggest to add this case to a Troubleshooting section in the Readme. Then is more visible for the angular users