-
-
Notifications
You must be signed in to change notification settings - Fork 7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Expose ActionManager.registerAction
through ExcalidrawImperativeAPI
#6995
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
size-limit report 📦
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Non-owner LGTM
@dwelle should check this for potential side effects that I don't see.
My concern would be it has many APIs I'd not consider stable. Further, the manager itself is possibly gonna be completely rewritten with respect to upcoming changes we're planning. Safer would be to expose just the /cc @ad1992 thoughts? |
@dwelle You have a good point about not exposing unstable APIs. The main use is actually I use |
Mhm, I'd probably wait with merging this post 0.17.0 npm release which should happen towards the end of next week, as it's likely we'll be touching these APIs after that. |
ActionManager
through ExcalidrawImperativeAPI
ActionManager.registerAction
through ExcalidrawImperativeAPI
…tiveAPI` (#6995) * feat: Expose `ActionManager` through `ExcalidrawImperativeAPI` * Only expose `registerAction` instead of `ActionManager`
For places where the "Rules of Hooks" preclude calling
useExcalidrawActionManager()
.