-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update the abstraction library code to use import type for interfaces #789
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We might want to setup an eslint rule to make sure we didn't forget anything and won't have any regression in the future. https://typescript-eslint.io/rules/consistent-type-imports/
Signed-off-by: Vincent Biret <[email protected]>
- adds headers inspection
Ping @koros |
My question was replied offline, still more work required on this one, and it might take a while. I'll go ahead and create the tags so we can at list have the community fix out. |
The eslint rule flags a lot more other instances which I have put some fix on the generation side. Let me do a final pass on this. |
…ub.com/microsoft/kiota-typescript into feature/use-import-type-for-interfaces
Generated "test-kiota-typescript-libraries" SDK package:
|
Generated sample app bundle:
|
Use
import type
whenever referencing the folowing interfaces: