Latest Contributions by AndyGup

I took a quick look and it looks like geopedia.ca is a self-hosted Portal? If so, it's possible something changed on their server-side CORS configuration. Otherwise, you'll need to do some testing to figure out which header within the app is triggering the error, or maybe you are missing a header. ... View more

@JoeHershman on the surface this sounds like a configuration issue within your environment. Can you open a support ticket? They can review your configuration in detail, there could be quite a few variables in play that are best investigated in a one-on-one support setting. ... View more

@BenRomlein A few things come to mind. You don't need a 3rd party module loader, such as dojo, when using ES modules. Also, JavaScript build tools need to be specially configured to interpret AMD or commonJS. Most implementations follow the ESM pattern: import xyz from "/mymodule/module"; Here's a link to a slightly older unofficial sample app that demonstrates using a custom widget with ES modules + TypeScript. https://github.com/kellyhutchins/arcgis-core-demo-app . And last, we do not currently recommend using the ArcGIS API for JavaScript ES modules with snowpack, for reference see this open issue: https://github.com/Esri/jsapi-resources/issues/299.  We do have a bunch of other build-tool samples to choose from, in the event you are able to switch away from snowpack: https://github.com/Esri/jsapi-resources/tree/master/esm-samples.  ... View more

Do you need to use local assets? It's not required, try commenting out esriConfig and see if your app works: // esriConfig.assetsPath = "./assets";  // comment out this line Additional reading: https://developers.arcgis.com/javascript/latest/es-modules/#working-with-assets ... View more

Based on what I see in the codepen, this isn't an issue with the ArcGIS API for JavaScript, something in your custom library injection code isn't working right. We recommend using esri-loader to lazy load the ArcGIS JS API: https://github.com/esri/esri-loader for exactly these types of use cases. ... View more

How are you copying your assets? Maybe delete the assets in your working directory and recopy just to make sure you have the most current ones. ... View more

Hi @bobypan8089 do you have a sample app or codepen that reproduces the issue? ... View more

Interesting, I think I understand your issue that there is a chain of synchronous DOM events after the parent widget has been created, and the question is whether or not the parent is aware when the final afterCreate event takes place. I'm just wondering, have you look at setting afterUpdate on the parent div? I can see there being potential problems with that but just in case here's the doc: https://maquettejs.org/typedoc/interfaces/vnodeproperties.html#afterupdate. Also on that page you can browse through all the event methods.  Reference: https://developers.arcgis.com/javascript/latest/custom-widget/#widget-rendering  ... View more

Hi @MartijnHoogstraten the short answer is no. What are you trying to do? Here's the widget life cycle events: https://developers.arcgis.com/javascript/latest/custom-widget/#widget-life-cycle.  ... View more

You'll need to use Angular data binding to pass data between the component class and the widget class, here's some additional info: https://angular.io/guide/two-way-binding and https://angular.io/guide/binding-syntax  ... View more

Oh, forgot to add that you might also take a look at this library: https://github.com/Esri/arcgis-rest-js/tree/master/packages/arcgis-rest-feature-layer  ... View more

Hi @Neberu note, this is not an issue with the ArcGIS API for JavaScript it's an issue with the manually created REST API requests. What's happening is the POST code is adding a header field that is triggering pre-flight. There's nothing in the JS API that would trigger pre-flight. One recommendation is to build a simple, vanilla JS app against a secured feature layer using the ArcGIS API for JavaScripts applyEdits() method and then compare the headers with your manually generated REST requests. Here's some psuedo-code to help you get started: //create feature layer const fl = new FeatureLayer({url: ". . .", apiKey:"your_key"}); // Add feature layer to map map.add(fl); const editFeature = new Graphic({ geometry: someValidGeometry, attributes: { attribute1: "TBD", attribute2: "TBD" } }); const edits = { updateFeatures: [editFeature] }; fl.applyEdits(edits) .then((editResults) => { console.log("edit results: ", editResults); }) .catch((error) => { console.error("Editing error: ", error); }) Additional info: * apiKey * https://community.esri.com/t5/arcgis-api-for-javascript/how-to-make-http-requests-work-with-axios-arcgisserver-amp-cors/m-p/1055674 ... View more