{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/d92d2c80d10b4ec98745a6223c5778e5\" frameborder=\"0\" width=\"1662\" height=\"1246\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1246,"width":1662,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1246,"thumbnail_width":1662,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/d92d2c80d10b4ec98745a6223c5778e5-6e2ec70c500845a4.gif","duration":109.7,"title":"Publishing Nodes with Schema Upserts","description":"This Loom explains a publishing workflow change to ensure node schemas are synced and upcerted before publishing nodes. First, when publishing results, it gathers the schema IDs, including node schema and node IDs, to calculate any missing node schemas, then upcerts those missing schemas and adds that update to the result. It emphasizes that nodes themselves are not upcerted. It also discusses a converter function change from OldStyleDiscourse node to a cross-app node schema to avoid a type error caused by introducing explicit local concept data input, which previously led to content being undefined."}