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 👋 I just switched to r169 from r156 and noticed that typedoc is giving a warning for the Camera class. I am getting this:
[warning] Failed to resolve link to "THREE.PerspectiveCamera | PerspectiveCamera" in comment for ...render-pass.BaseCamera.constructor.
[warning] Failed to resolve link to "THREE.OrthographicCamera | OrthographicCamera" in comment for ...render-pass.BaseCamera.constructor..BaseCamera.constructor.
The reason it happens for me is because I am extending the Camera class to create my own BaseCamera class like this:
export class BaseCamera extends Camera { }
But I believe typedoc would give this warning for every other doc-string where namespace THREE is being used since this namespace has entirely been removed. Is it possible to update the doc-strings so that they are typedoc compliant? :) Also let me know if its something wrong on my side or I should approach this differently. Thanks! 🙏
PS. I can also volunteer to fix the links so that they don't use the THREE namespace anymore.
The text was updated successfully, but these errors were encountered:
AdilRabbani
changed the title
Typedoc failing for locations where namespace THREE is being used in r169
Typedoc warnings for locations where namespace THREE is being used in r169
Oct 23, 2024
Hi 👋 I just switched to r169 from r156 and noticed that typedoc is giving a warning for the
Camera
class. I am getting this:The reason it happens for me is because I am extending the
Camera
class to create my ownBaseCamera
class like this:But I believe typedoc would give this warning for every other doc-string where namespace
THREE
is being used since this namespace has entirely been removed. Is it possible to update the doc-strings so that they are typedoc compliant? :) Also let me know if its something wrong on my side or I should approach this differently. Thanks! 🙏PS. I can also volunteer to fix the links so that they don't use the
THREE
namespace anymore.The text was updated successfully, but these errors were encountered: