David Luzar

The opposite. We currently use [string names for actions](https://github.com/excalidraw/excalidraw/blob/ecbd5ba55d6af86dcc533dda2242ccb134bac570/src/actions/types.ts#L25), while to execute them, we [supply the action object](https://github.com/excalidraw/excalidraw/blob/ecbd5ba55d6af86dcc533dda2242ccb134bac570/src/actions/manager.tsx#L88). I want to get rid of the string names altogether.

To keep the API simple, having two ways to refer to actions isn't gonna achieve. I think exporting the actions won't do any harm.

> I meant lets only allow by name so the host doesn't have to import the action as well to execute and API will also be simple. Why? Exporting the...

The use case you link to can be achieved by comparing to the action objects, which will be better anyway coz it'll be explicit, typed, and more accessible. And that...

@karlhorky hi, we're working on this as part of https://github.com/excalidraw/excalidraw/pull/8012 and followups!

we are indeed planning keyboard customization, but there's a series of steps we need to make, one of which is rewriting the keyboard handling from the ground up, which won't...

A few considerations: - [ ] the font has slightly different dimensions from the previous one (see the boxes below), which will potentially break existing diagrams layout. We could work...

> > I'm wondering if the new CJK font won't cross that line much more. > > To me, it looks like beautiful pen drawn, and less hand-drawn. > I...

> I mean it looks different and I can't read some of them. So, even if the char code is the same, we can't use the same font for Chinese...

> @dwelle True. We can't simply use Chinese font for Japanese. AFAIK, it's the mistake of Unicode that tries to share the char code that looks "similar" in Chinese and...