Found an issue related to mapping objects to schema definitions. This comes up in particular when an OEM extension is not providing @odata.type. The tool tries to dynamically map a definition and keep stepping into properties, but hits a point where it will break down on leaf properties. The change adds a missing return statement when it finds the property is not an object; not returning there guarantees an exception when it tries to pull out its @odata.type property.
Long term it might be worth rechecking this flow to not even attempt to map it in the first place, but that might take more time than its worth at the moment.
Found an issue related to mapping objects to schema definitions. This comes up in particular when an OEM extension is not providing
@odata.type. The tool tries to dynamically map a definition and keep stepping into properties, but hits a point where it will break down on leaf properties. The change adds a missing return statement when it finds the property is not an object; not returning there guarantees an exception when it tries to pull out its@odata.typeproperty.Long term it might be worth rechecking this flow to not even attempt to map it in the first place, but that might take more time than its worth at the moment.