Seeing issues with the Typescript definitions for attributes on arcgis-map.
/**
* This gives a type error for Geometry because the signature for Feature | Point can't handle partial values
* Note: the value for constraints is taken directly from documentation
**/
const testMap1 = (
<arcgis-map constraints={
{
geometry: { // Constrain lateral movement to Lower Manhattan
type: 'extent',
xmin: -74.02,
ymin: 40.7,
xmax: -73.971,
ymax: 40.73,
},
minScale: 500000, // User cannot zoom out beyond a scale of 1:500,000
maxScale: 0, // User can overzoom tiles
rotationEnabled: false, // Disables map rotation
}
} />
);
/**
* Defining the constraints object separately gives type safety for the object, but then gives a type error when we try to use it in the map component
* In this case, the issue is that MapViewConstraints treats optional fields as required
**/
const testConstraints: MapViewConstraintsProperties = {
geometry:
{ // Constrain lateral movement to Lower Manhattan
type: 'extent',
xmin: -74.02,
ymin: 40.7,
xmax: -73.971,
ymax: 40.73,
},
minScale: 500000, // User cannot zoom out beyond a scale of 1:500,000
maxScale: 0, // User can overzoom tiles
rotationEnabled: false, // Disables map rotation
};
const testMap2 = <arcgis-map constraints={testConstraints} />;
/**
* Coercing the type works, but we shouldn't have to do this
**/
const testMap3 = <arcgis-map constraints={testConstraints as MapViewConstraints} />;
