David Luzar
David Luzar
the "progress" commit [`16a2431` (#6086)](https://github.com/excalidraw/excalidraw/pull/6086/commits/16a2431fd8f1296663fb63a322f6c739c2fb2dbd) adds a tons of unreadable code in an attempt to handle/fix more cases, but I still didn't get right when `x`, `y`, `width`, `height`, `padding`,...
Considering IndexedDB is also worthwhile if we end up storing collab scenes in separate entries in which case we could quickly run out of the 5MB localStorage limit.
hey @DanielJGeiger, thanks for the PR. I've left some comments. As for the action guards, does it solve anything that cannot be solved using the `predicate` right now?
Another use case for increased storage: multiple scenes https://github.com/excalidraw/excalidraw/issues/1543#issuecomment-624817976
I think migrating directly should be fine. Almost every `localStorage` access is located in `src/data/localStorage.ts`. The consumers will need to be rewritten to be async, though.
@excalibot trigger release
Package seems to work, but for some reason it's breaking the example https://excalidraw-package-example-git-fork-aloento-master-excalidraw.vercel.app/
@Aloento @ad1992 I'd actually love to merge this if we figure out the way to fix the `react-dom/client` & `react/jsx-runtime` thing
Hi. Changing the settings in the export dialog extends to the clipboard export actions, too! Also, when you select an element, the export dialog will contain an option to toggle...
> This is so awesome that you are trying this out. I think we can even make a PR to tunne-rat to add an API to declare a fallback with...