Timeline for Extended KeywordModel with metadata fails when metadata empty
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 18, 2018 at 17:28 | comment | added | Rick Pannekoek |
Based on the R2 JSON you provided, it seems that in the problematic scenario, the CM Keyword doesn’t have metadata (nor a metadata Schema) at all. As a result, there is no Schema ID in the JSON and as a result of that, the semantic mapping logic gets confused and instantiates KeywordModel instead of HotelKeyword.
|
|
| Jul 17, 2018 at 14:51 | comment | added | tfinez | I don't get it. It's not that the Hotel.name is empty, but when it fails is when Hotel.name.nearbyHotels is empty. | |
| Jul 17, 2018 at 11:06 | comment | added | Rick Pannekoek | Ah, now I get it. I have updated my answer. Seems like bug, indeed, but hopefully with a work-around possible. | |
| Jul 17, 2018 at 11:06 | history | edited | Rick Pannekoek | CC BY-SA 4.0 |
added 1164 characters in body
|
| Jul 17, 2018 at 8:55 | comment | added | tfinez | I added more comments. We think we found a new bug in the product. | |
| Jul 13, 2018 at 13:50 | history | answered | Rick Pannekoek | CC BY-SA 4.0 |