Latest Contributions by ReneRubalcava

‎05-12-2021

How are using the registerToken? Not exactly secure, but you could pass the token via URL to your sub-app, create a new credential with the token and register it. You'd need the serverInfo, maybe the expiration too in case the app stays open for days/weeks. I thought the tokens were stored at the root domain level, but maybe url specific.

‎05-12-2021

As much as I'm a fan of AOP, you don't really need it in this case. It looks like you are updating the titles in the legend. You can wait until the query is done, watch the layer or watch for changes in the activeLayerInfos collection, if that will be updated. Change the title of the layer and it will be reflected in the legend. You should avoid modifying the DOM of widgets as there's no guarantee the changes will stick. That's why you're waiting for the scheduleRender method to fire, but I think you can change your workflow to avoid that use case.

‎05-12-2021

If you add a .catch() to the promise chain will you get the error that a token is required?

‎05-12-2021

You can set the PopupTemplate overWriteActions to true and don't provide an actions array. https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html#overwriteActions This will remove it.

‎05-12-2021

Everything you need for DOM navigation in native to JavaScript these days. https://developer.mozilla.org/en-US/docs/Web/API/Document/querySelector

‎05-10-2021

I don't know if this was available when this post was made, maybe, and I missed it, happens. But the layers have a property called customParameters you can use to add tokens like this. https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-FeatureLayer.html#customParameters In this case, you can avoid using an interceptor to add url params.

‎05-06-2021

Yes, you will still get about 300 js files in a built app with rollup. You won't use them all, but because of dynamic module loading and the way rollup chunks files, you get a good amount of them. This because depending on your data, you could use them. This is completely expected. You'd maybe use a dozen or so at runtime.

‎05-06-2021

You can apply a renderer to a polygon layer to display them as points. const polygonAsPointRenderer = { type: "simple", symbol: { type: "simple-marker", color: [247, 53, 53, 1] } } You can apply visual variables or use unique value renderer to meet your visualization needs too.

‎05-06-2021

If you're using 4.19, you don't need to copy the assets anymore, you can remove that script from your package.json. https://developers.arcgis.com/javascript/latest/release-notes/#assets-for-local-builds That will cut down on all those extra files.

‎05-05-2021

On the version mismatch, we a couple of patches, and it just lets you know. Since it's still 4.19, you should be ok. Warnings won't break anything. You can point to the correct version of 4.19 using jsdelivr as described here. https://community.esri.com/t5/arcgis-api-for-javascript/warning-version-mismatch-detected-between-arcgis-api-for/m-p/1054757#M72938

‎05-05-2021

You could point the assets to the specific version you want to match using jsdelivr https://www.jsdelivr.com/ Typically, these warnings don't have much impact at the patch level. For production, if you want to be completely bullet-proof, you can use jsdelivr or copy the assets. And we don't typically patch the CDN post-release, just something came up. NPM would only get patched if I messed something up, which has happened before... my bad.

‎05-05-2021

I can add to this that I have tested a single file bundle. using webpack and you pretty much end up with a 7mb js file with tons of code you probably won't use at runtime.

‎05-04-2021

You could use various methods of the geometryEngine to validate that geometries intersect or that a vertex matches a point https://developers.arcgis.com/javascript/latest/api-reference/esri-geometry-geometryEngine.html It might require breaking up polygons -> polylines -> points, but should be doable.

‎05-04-2021

If you want to use node packages, you'll need to use some sort of build tooling. That demo just compiles the TS to JS, but does no bundling of any sort. Tools like rollup and webpack can do that for you. https://github.com/Esri/jsapi-resources/tree/master/esm-samples https://github.com/Esri/jsapi-resources/tree/master/4.x/webpack/demo If you are just getting started, the cli might be useful to try. https://github.com/Esri/arcgis-js-cli

‎05-04-2021

Hi there! Can you update the dojo-util to use our fork please. "devDependencies": { "dojo-util": "git+https://github.com/Esri/dojo-util.git#1.16.3-esri", }, We use an updated version of the closure compiler that will fix this issue for dojo builds. Thanks!

Online Status	Offline
Date Last Visited	Wednesday

My Ideas

Latest Contributions by ReneRubalcava

Re: Multiple Apps

Re: What can I use instead of dojo/aspect and dojo/query - ArcGIS 4.19 API

Re: esrRequest does not handle missing token

Re: Not able to hide zoomto button on popup

Re: How do we query an app's dom without dojo/query?

Re: How do I add a secured feature service using a token in 4.X?

Re: Svelte jsapi 4.19: Tons of Build Files

Re: Drawing centroid for polygons

Re: Svelte jsapi 4.19: Tons of Build Files

Re: ES Modules (v4.19) throwing CORS errors

Re: Warning: Version mismatch detected between ArcGIS API for JavaScript and assets

Re: How to bundle @arcgis/core files in Angular build?

Re: Snapping Enforcement/Confirmation 4.19

Re: Import and use a Node Package

Re: ArcGIS API 4.19 Dojo build failure

Re: Popup Component Title Font Size

Re: playwright and arcgis js sdk e2e tests

Re: esriConfig.portalURL and <arcgis-map> componen...

Re: Trouble Using Reactive Utils On Initially Unde...

Re: Custom Component Shadow DOM not fully loaded o...