Describe the bug
When cloning a Site, the basemap information is not copied to the correct node in the json structure. This results in a number of off behaviors in the cloned site.
Steps To Reproduce this behavior
Clone a Site
View the data.json of the original site and the clone
You'll see that the original has the baseMapLayers and title properties nested under data.values.map.basemaps.primary
But the clone has those directly under data.values.map
Expected behavior
basemap information should be located at data.values.map.basemaps.primary
Observed behavior
basemap information is located at data.values.map
Screenshots
n/a
Additional context
In order to address asap and not wait for a python api release, the Hub application will add code to remedy this during the load cycle, but the underlying issue should be addressed asap so it's in the next release
Describe the bug When cloning a Site, the basemap information is not copied to the correct node in the json structure. This results in a number of off behaviors in the cloned site.
Steps To Reproduce this behavior
baseMapLayers
andtitle
properties nested underdata.values.map.basemaps.primary
But the clone has those directly under
data.values.map
The issue is https://github.com/Esri/hub-py/blob/fbf85069aaf711dd0ebc8781f1dbdbd78969e393/arcgishub/sites.py#L736
Expected behavior basemap information should be located at
data.values.map.basemaps.primary
Observed behavior basemap information is located at
data.values.map
Screenshots n/a
Additional context In order to address asap and not wait for a python api release, the Hub application will add code to remedy this during the load cycle, but the underlying issue should be addressed asap so it's in the next release