You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed a discrepancy between how the interface SiteDefinitionLanguage defines Url and UrlSegment and what is returned from the Content Delivery API. In the API response these members are called url and urlSegment. Trying to access Url will always result in undefined.
The text was updated successfully, but these errors were encountered:
Camel case is commonly used in JavaScript, that's why properties start with lowercase. JavaScript (JSON) is case-sensitive, and that's why you're getting undefined, i.e. there is no property called Url. This is the case for all objects returned by the REST API, at least for all built-in properties, the exception is your custom properties which will have the casing you have defined them with.
I noticed a discrepancy between how the interface
SiteDefinitionLanguage
definesUrl
andUrlSegment
and what is returned from the Content Delivery API. In the API response these members are calledurl
andurlSegment
. Trying to accessUrl
will always result inundefined
.The text was updated successfully, but these errors were encountered: