WHAT DO YOU RECOMMEND
Currently, tables in objects created through the local REST API (from a markdown body) render at a minimal default width, with every column collapsed and text heavily wrapped. There is no way to set table or column width programmatically. Tables created via the API should default to the full editor width (columns distributed to content), or the API should expose a table/column width attribute.
REAL WORLD USE CASES
Bulk-importing documents via the API — e.g. migrating Word meeting notes into a space. Every note contains metadata and content tables, and all of them come in squeezed and have to be widened by hand one table at a time, which defeats the point of a programmatic import.
RECOMMENDED ALTERNATIVES
Expose the existing page-level “full width” layout toggle as an API property, so imported pages can at least use the wider canvas.
ADDITIONAL CONTEXT
Example after import:
