{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/82c15eed4c4d4c45b77d92d6d7d406d2\" 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/82c15eed4c4d4c45b77d92d6d7d406d2-963a43c20ca1ca37.gif","duration":102.204,"title":"Making Subtype Mandatory and Fixing Tests","description":"This Loom explains a PR change to make a subtype mandatory to avoid an earlier problem. The author argues it should always be provided even for HTTP-based platforms like Roam, despite the possibility it will be discarded, and notes this requires adding it to the source because it is now required. They say the main origin of the issue was getConceptMap, and they derive the subtype value from necessary flags, fixing a test in the process. New tests were added to check that RIDs are correct per Don Nguyen’s guidance, and an additional commit defines allowed type values to prevent a node versus node mistake."}