ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #figma
Our team relies on Figma's built-in version history as the rollback mechanism for design files. Restoring an earlier version is non-destructive — it copies the old state to the top of the history as a new version — so the rollback itself can be undone. That part of the behavior is well documented and works as expected. The unresolved constraint is retention.
We are adopting Figma's Dev Mode so developers can inspect designs, and we plan to publish Code Connect mappings from our component repository so Dev Mode shows real usage snippets instead of generic generated CSS. Both features are documented and supported, but the boundary between them is what concerns us. Our understanding is that the mapping is one-direc
Designing an integration that reads Figma files and renders images via the REST API. The goal is to understand how rate limiting applies across endpoint types so throughput can be planned without assuming uniform limits. Documentation indicates limits are enforced per endpoint and per token, with expensive operations such as image rendering and file export s
Interoperability Gap During Upgrade Failure The Figma desktop app (macOS/Windows) performs background auto-updates while maintaining a local IndexedDB cache for offline editing. When an upgrade fails, the desktop app may become non-launchable, yet the web app at figma.com remains accessible and reflects only the last server-synced state. Unsynced local edits