{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/713b68611c90472b9306f02ad39bc6b5\" 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/713b68611c90472b9306f02ad39bc6b5-be77643b992718c6.gif","duration":95.129,"title":"Hoisting Title Collision Checks for Assets","description":"This Loom explains how a PR ties together node asset import and a title collision failure fix. It notes that previously the title collision failure code landed “here and there,” but now it is executed earlier in another part of the code so assets do not need to be reverted. Because reverting asset creation is difficult due to concurrency between different users, the title collision failure check is hoisted into this location. It mentions that the factored out code comes from the earlier places where it was done after a different moment."}