@ericdrobinson Would you mind taking a look at this? Thank you very much in advance 🙂

@pklaschka I've done a first-pass review and hit the major points, I think. Basically:

1. You might want to go through and do a pass on @example code to clean it up. I saw other locations throughout the code base with similar issues to those pointed out above.
2. You might want to go through and remove the intra-documentation link formatting. It linkifies in the IntelliSense but shows an error if you click it.
3. Adding BLEND_MODE_*s to the SceneNode base class definition causes it to appear in all subclasses. A different approach should be determined here. You might try resurrecting the SceneNode interface (and reverting all that SceneNodeClass stuff), add those properties to the SceneNode interface, and then declare a SceneNode name of a type that only contains the various "static properties" and export that.
   • Note that you do not want to export something like SceneNode: SceneNode because it would contain all the properties/methods of the SceneNode class which the actual SceneNode object you get in Xd from the scenegraph module has nothing public on it but standard Object stuff and the properties.

@pklaschka With respect to the third item above, something like this looks to work a treat:

// Define the shape of the SceneNode "restricted" static properties.
//  NOTE: These properties do not show up on sub-classes so they cannot
//  be a part of the class-inheritance tree.
interface SceneNodeStatic {
    readonly BLEND_MODE_PASSTHROUGH: string;
    readonly BLEND_MODE_NORMAL: string;
    readonly BLEND_MODE_MULTIPLY: string;
    readonly BLEND_MODE_DARKEN: string;
    readonly BLEND_MODE_COLOR_BURN: string;
    readonly BLEND_MODE_LIGHTEN: string;
    readonly BLEND_MODE_SCREEN: string;
    readonly BLEND_MODE_COLOR_DODGE: string;
    readonly BLEND_MODE_OVERLAY: string;
    readonly BLEND_MODE_SOFT_LIGHT: string;
    readonly BLEND_MODE_HARD_LIGHT: string;
    readonly BLEND_MODE_DIFFERENCE: string;
    readonly BLEND_MODE_EXCLUSION: string;
    readonly BLEND_MODE_HUE: string;
    readonly BLEND_MODE_SATURATION: string;
    readonly BLEND_MODE_COLOR: string;
    readonly BLEND_MODE_LUMINOSITY: string;
    readonly FIXED_LEFT: string;
    readonly FIXED_RIGHT: string;
    readonly FIXED_TOP: string;
    readonly FIXED_BOTTOM: string;
    readonly FIXED_BOTH: string;
    readonly POSITION_PROPORTIONAL: string;
    readonly SIZE_FIXED: string;
    readonly SIZE_RESIZES: string;
}

// Export the "name" of SceneNode. This provides access to the "restricted" static
//  properties.
// You could get the "type" of this by using `typeof SceneNode` (especially in type
//  declarations).
export const SceneNode: SceneNodeStatic;

// Export the "type" of SceneNode. This provides access to the "SceneNode" _type_.
export interface SceneNode extends SceneNodeBase {}

/**
 * Base class of all scenegraph nodes. Nodes will always be an instance of some subclass of SceneNode.
 */
declare abstract class SceneNodeBase {

NOTE: In the above, I renamed SceneNodeClass to SceneNodeBase as it better describes what its purpose is.

During my investigation I saw a few things that don't quite match up with this structure but it was nothing actually usable. Just differences in accessible prototype properties/functions. In terms of what is documented by Adobe and what you would want to use these APIs for, the structure I outline in this comment seems to work beautifully.

Thank you so much for your input. I'm currently dealing with an ear infection (cf. my comment in the developer forum) and am unable to work on this, but I will look at it as soon as possible. Thank you again 👍.

Yikes! Take care and I wish you a swift recovery!

@ericdrobinson:
You might want to go through and remove the intra-documentation link formatting. It linkifies in the IntelliSense but shows an error if you click it.

Truthfully, I wasn't able to replicate it. VSCode just doesn't link (at all) and WebStorm handled it fine (correctly linking). Do you have any examples where it wasn't working for you (I know it's been quite some time since your comment, sorry about that 😉 )?

Truthfully, I wasn't able to replicate it. VSCode just doesn't link (at all) and WebStorm handled it fine (correctly linking). Do you have any examples where it wasn't working for you (I know it's been quite some time since your comment, sorry about that 😉 )?

Yes. If you attempt to use scenegraph.getNodeByGUID() in VSCode, the IntelliSense will appear like so:

Note that "guid getter" is shown as a link in VSCode's IntelliSense view. If you click that link, you get the following error:

The links do not work.

It turns out that intra-API linking in IntelliSense is not supported by the TypeScript language server. This TypeScript issue is tracking interest/development.

While this does appear to work in WebStorm (and other JetBrains IDEs), any IDE that relies on the TypeScript Language Server (most non-JetBrains IDEs?) will report errors when you attempt to use this syntax.

That all said, the workaround would be to point to the Adobe XD documentation website. In the case outlined above, this would mean converting this:

[`guid` getter](#SceneNode-guid)

to this:

[`guid` getter](https://adobexdplatform.com/plugin-docs/reference/scenegraph.html#SceneNode-guid)

In my tests, this appears to work perfectly. Clicking that link opens the expected dialog in VSCode: