<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/0326879f84d545428defd6591d079149&quot; frameborder=&quot;0&quot; width=&quot;2580&quot; height=&quot;1935&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1935</height><width>2580</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1935</thumbnail_height><thumbnail_width>2580</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/0326879f84d545428defd6591d079149-213f047020316a4d.gif</thumbnail_url><duration>244.016</duration><title>Debugging Mission Tree User.js and HTML</title><description>This Loom explains the developer’s work and debugging on a mission tree project, focusing mainly on issues in user.js. The author notes that JavaScript is case sensitive and had to change the property used for the displayed username from “person full and last name” to the exact “full name” to match the class gate requirement. They also describe converting user text inputs to numbers for salary and expense calculations using number conversion, and creating an expenses array to store expense IDs. Finally, they mention additional unresolved confusion in the user.js return logic, where they previously returned first name and last name instead of the full name.</description></oembed>