You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi.
As the title suggests.
It seems to be oriented towards the deprecated source of the createClient definition, even though the second argument is not passed.👋
Also, by modifying contentful-management.d.ts as follows
The definition source is now oriented to the createClient, which can be expected.
(I don't think this is in line with best practice, but... ,)
I am not very knowledgeable in this area, so please can someone lend me their knowledge🙏
Hello everyone, thanks for bringing this up. It appears that this is an error in the IDE and we found a way to mitigate this. There is a more detailed explanation in the linked PR. As recommended by you, I adjusted the warning so that is "followed by a sentence describing the recommended alternative". It doesn't say that one should link to another function and I found it not very intuitive to link to other overloads, so I decided to leave that out and describe with words what one should do.
Hi.
As the title suggests.
It seems to be oriented towards the deprecated source of the createClient definition, even though the second argument is not passed.👋
The following is a following the README of contentful-typescript-codegen
The code for getContentfulEnvironment.js created in the root of the project.
As you can see below, is it possible that
@deprecated
is affecting the overload?I felt that Is this a phenomenon that I am the only one reproducing?
(If so, I felt it necessary to review the VSCode settings, etc.)
microsoft/tsdoc#131
Also, by modifying
contentful-management.d.ts
as followsThe definition source is now oriented to the createClient, which can be expected.
(I don't think this is in line with best practice, but... ,)
I am not very knowledgeable in this area, so please can someone lend me their knowledge🙏
Versions are as follows:
"contentful-management": "10.29.4"
[imo]
I also thought that
@deprecated
should include a recommendation of what should be used instead, so I thought we should follow convention.The text was updated successfully, but these errors were encountered: