[Feature Request]: Document the new extension API?

[melMass]

Is there an existing issue for this?

• I have searched the existing issues and checked the recent builds/commits

What would your feature do ?

Hi,

I'm migrating to ts and use the published types which showed a deprecation:

But the docs still mention the old way and I can't find how to use this new "hook" / provider concept

Proposed workflow

Add documentation for useExtensionService

Additional information

No response

┆Issue is synchronized with this Notion page by Unito

[christian-byrne]

I belive the deprecated is meant as an internal note. However, since registerExtension is definitely a part of the public API, we should probably remove that comment altogether. Thanks for pointing that out, that's pretty bad for such a central part of public API to call itself deprecated

[melMass]

Thanks!
I found another one useExecutionStore:

[christian-byrne]

Nice catch. Besides ComfyApp.runningNodeId there seems to alo be some other "deprecated" public ComfyApp methods nearby.

I think immediate action could be to add certanin executionStore methods to the return value of the extension manager, and extending the interface accordingly. Then we adjust the deprecation note.

This requires some thought about which abstract methods of executionStore we can/should support in public interface going forward.