I can't provider a minimal repro sample. Like I said, this is an extension that sits inside another application.
> One suggestion is to first build the custom layer in JavaScript, and then migrate your code to TypeScript.
Well that speaks exactly to my question, doesn't it? I can't subclass - I have to use @subclass, which is a hack (and which doesn't work). I can't just import, I need to use loadModules, which is a hack. If it's not dojo, fine - but when will you produce a clean SDK that follows web standards, with regular types without all of these hacks throughout your system? There's no need for all of this "cleverness".
Here's another delightful example; this previously working code results in:
Accessor#set Assigning an instance of 'esri.geometry.SpatialReference' which is not a subclass of 'esri.geometry.SpatialReference'
addLine1(coords: CRTM05Coordinates[][], color: string, width: number): number {
const line = new Polyline({
paths: coords.map(ring => ring.map(point => [point.east, point.north])),
spatialReference: this.w.view.spatialReference
});
return this.addLine2(line, color, width);
}
(This is, btw, "fixed" by ` spatialReference: { wkid: this.w.view.spatialReference.wkid }`).
Yet another example:
this.graphicsLayer = new GraphicsLayer({
title: "My graphics layer"
});
// Add the graphics layer to the map
this.w.map.add(this.graphicsLayer);
Results in:
#add() The item being added is not a Layer or a Promise that resolves to a Layer.
This is fixed by:
loadModules(['esri/layers/GraphicsLayer']).then(([GraphicsLayerClass]) => {
this.graphicsLayer = new (GraphicsLayerClass as typeof GraphicsLayer)({
title: "My graphics"
});
// Add the graphics layer to the map
this.w.map.add(this.graphicsLayer);
});
...despite the underlying site already having initialized via:
require([
...
'esri/layers/GraphicsLayer',
