BasemapGalleryProperties `source` TypeScript definition autocast missing
See original GitHub issueI am reporting an issue with
- TypeScript definitions
- another resource in this repository
According to index.d.ts, BasemapGalleryProperties
has the following:
source?: LocalBasemapsSourceProperties | PortalBasemapsSourceProperties;
But the docs for source
clearly state that it can take an array or Collection and autocast it.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
MapView | API Reference | ArcGIS Maps SDK for JavaScript ...
Represents the view for a single basemap after it has been added to the map. breakpoints Object. A convenience property used for defining...
Read more >Solved: Adding Custom Basemaps to Basemap Gallery in 4.3
The source for basemaps that the widget will display. This property can be autocast with an array or Collection of Basemaps, a Portal...
Read more >How to add multiple colors inside the cluster of points ... - GitHub
Hi nick, We really liked your flare cluster layer.In my requirement I want to show multiple default symbols based on the condition.
Read more >GEOG 863 - John A. Dutton e-Education Institute
In this course, we'll be spending the bulk of our time learning how GIS web applications can be built using a mapping Application...
Read more >Release notes for 4.13 | ArcGIS API for JavaScript 4.18
Now you can symbolize layers using a dictionary of symbols configured with multiple attributes. For example, you may want to symbolize alternative fuel ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
No, not worth it. We’ll move to TS soon enough which can produce AMD modules just fine.
Yes, we recommend using imports, which are made easier in VS Code with it’s auto-importing.