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
depending on the timeline of the removal, some possible solutions:
remove the flag to strip out comments
in the above typescript issue is a workaround mentioned, essentially compiling twice: once for javascript, once for the ambient types. I don't think it's worth the trouble.
one could (search and) inject the @ deprecated tag after the build into the ambient files.
do nothing, leave as is - might be removed soon anyways
or better, one could also use the node.js wrapper function util.deprecate() which essentially writes a deprecated message [once for the lifetime of the application] to the console. doing so would notify javascript and typescript users regardless of what IDE has been used.
I can also provide a PR with the suggested wrapper.
The text was updated successfully, but these errors were encountered:
Thanks @dnalborczyk, I like the last suggestion and TIL. Since these warnings are natively suppressible I'd certainly entertain a PR which implements this 👍
because of this issue any jsdoc @ deprecated tags are not discoverable by users. e.g. this one:
federation/federation-js/src/service/buildSubgraphSchema.ts
Line 137 in 71e0dd1
depending on the timeline of the removal, some possible solutions:
or better, one could also use the node.js wrapper function util.deprecate() which essentially writes a
deprecated
message [once for the lifetime of the application] to the console. doing so would notify javascript and typescript users regardless of what IDE has been used.I can also provide a PR with the suggested wrapper.
The text was updated successfully, but these errors were encountered: