Latest Contributions by ReneRubalcava

Thanks for that! Helps with some context. The more I think about it, for now anyway, is don't use the item-id directly on the map/scene component. Create the webmap first, set your config props, then assign the map to to component. import "@arcgis/map-components/components/arcgis-map"; import config from "@arcgis/core/config.js"; import WebMap from "@arcgis/.core/WebMap.js"; config.portalUrl = "mydomain.com/arcgis"; const map = new WebMap(...); const viewElement = document.querySelector("arcgis-map"); viewElement.map = map; We'll think about this pattern some more. I think our current doc is more CDN focused here. https://developers.arcgis.com/javascript/latest/authentication/access-tokens/ This sample is more about setting OAuth, but I think the same pattern would apply to setting the config props too. https://github.com/Esri/jsapi-resources/tree/main/templates/js-maps-sdk-vite ... View more

Do you have a small demo of this behavior? I think import config and components in same module would cause this issue, depending on your app. In something like React, loading config with comps should work because the render of the component happens after you probably set the config settings. If you're app loads the components and the config and you already have <arcgis-*> elements on the page, then I can see where this could be an issue, they would get hydrated right away, maybe before your config set up is done. Let us look at this a little further and see what can be done. ... View more

This is a great sample, and has a11y testing! Thank you, always love to see that! ... View more

We don't have any doc directly for this, but Playwright tests everything in the browser, so you would use Playwrights test method that returns a page method for selection you can use. https://playwright.dev/docs/api/class-test I don't have anything on hand to demo, but interaction with map and other widgets/components should be same as other HTML elements. I think trickiest part would be trying "click" on a feature to show popup, that I'm not sure on. But you can use page selectors to click buttons and other bits and test for UI state. Is there a particular error or workflow you are getting blocked at with it? ... View more

Maybe it's a settings somewhere. I used our create CLI to make this angular app and I can get the ready state. ReneRubalcava_0-1777053398734.png Here is a github repo, maybe something in the angular.json can help? I'm not an Angular expert, so can't say for sure. https://github.com/odoe/arcgis-angular-lifecycle/blob/main/src/app/app.html ... View more

As Anne mentioned, if you can provide feedback on what your level of customization is, that would help us with our planned work. On knowing when things are done, it gets a little tricky component to component. componentOnReady promise lets you know the component has been initialized and rendered once, fully loaded. This doesn't mean it's done loading though. A component like TimeSlider is still gathering info from the layers and map and could update again. It's useful to know when default values are assigned or when you can use methods on a component. arcgisReady event lets you know that the component has a reference to the underlying view rendering the map. Meaning it can now communicate with the map. But again, it doesn't mean that the component is done working and could update its UI. One option is to listen for the arcgisPropertyChange event and check for when the state property changes to ready. You can try this to see if it has done rendering with all the data that it needs. timeSlider.addEventListener("arcgisPropertyChange", (event) => { // Check for state change if (event.detail.name === "state") { console.log("Property change name: ", event.detail.name); console.log("Property change value: ", event.target[event.detail.name]); // if state is "ready", try checking for UI changes } }); Demo: https://codepen.io/odoe/pen/NPRVxzO?editors=1000 ... View more

This will depend on how you are building your app. They key is to set this up before the map-components load or added to the DOM. One good way is to set them on the global esriConfig object. https://codepen.io/odoe/pen/LYaveKr <head> <script> // use the global esriConfig variable to initialize properties var esriConfig = { // No map will load with fake portal portalUrl: "https://myHostName.esri.com/arcgis" }; </script> <script type="module" src="https://js.arcgis.com/5.0/"></script> </head> <body> <arcgis-map item-id="d5dda743788a4b0688fe48f43ae7beb9"> <arcgis-expand slot="top-right"> <arcgis-search></arcgis-search> </arcgis-expand> <arcgis-legend slot="bottom-left"></arcgis-legend> </arcgis-map> </body>   You can also use a script tag in the <head> to set this up. Then you can write your app code in a script tag in the last element of the body. https://developers.arcgis.com/javascript/latest/programming-patterns/#set-the-portalurl-in-a-cdn-application Another way is to create the WebMap yourself and assign it to the map component. https://developers.arcgis.com/javascript/latest/programming-patterns/#using-webmap-or-webscene https://developers.arcgis.com/javascript/latest/programming-patterns/#set-the-portalurl-in-an-esm-application   ... View more

The equivalent to manual would be the default slot, basically don't name a slot and it goes into the default location. https://developers.arcgis.com/javascript/latest/references/map-components/components/arcgis-map/#slot-default Here's a demo: https://codepen.io/odoe/pen/ZYpWjXQ?editors=1000 ... View more

You hit the nail on the head with the casting. This is how you can get the action typings you are looking for. We can look at this further and see if we can infer this in a future release, but that is the current solution. ... View more