Latest Contributions by LefterisKoumis

This page is titled "Use Map Components (React 19 + Web Components)" and it provides instructions to download the SDK to a new folder on your ExB development environment called "web-component-widgets/use-web-components-19". React JS 19 uses functional components. Under the "Contents" version it states: The issue I see is that at the SDK location it still uses class components. For example, the "add-layers" sample it states that it was updated to version 1.19 but the script suggests otherwise.   render () { const style = css` form > div { display: flex; justify-content: space-between; input { width: 100%; } button { min-width: 100px; } } ` return ( <div className="widget-addLayers jimu-widget p-2" css={style}> {this.props.hasOwnProperty('useMapWidgetIds') && this.props.useMapWidgetIds && this.props.useMapWidgetIds.length === 1 && ( <JimuMapViewComponent useMapWidgetId={this.props.useMapWidgetIds?.[0]} onActiveViewChange={(jmv: JimuMapView) => { this.setState({ jimuMapView: jmv }) }} /> )} <p>{defaultMessages.instructions}</p>   ... View more

The Experience Builder online documentation needs badly a update on all pages to reflect the changes that come with ArcGIS ExB 1.19, ReactJS 19 and Node JS 22. For example, the ExB starter widget as instructed here, it cannot be implemented as described because you will get a webpack error due to incompatibility with the newer version of Node.js. In the newer versions of React JS., only function based components are used, but sadly most of the ESRI ExB documentation still refer to the class based components. @Jianxia  ?   ... View more

When the layer-url property is not set at design time, <arcgis-feature-table> shows the layer list icon with the message “No layer”, even if users add layers later during runtime. Is there a way to replace this message with something like “Click the icon to display tables for available layers”? As it stands, users are not clearly informed that clicking the icon reveals the list of feature tables. @Sage_Wall @ReneRubalcava  ... View more

In the past, I stayed away from building custom widgets in Experience Builder because layer selection had to be done at design time. I was recently informed that widgets can now dynamically work with any layers currently on the map. Since it’s been a while, I need to refresh my React skills—specifically, which React 19 component concepts should I focus on? ... View more

I am using the example as posted here to calculate the geodetic length and area of a location. Wanted to use imperial units (ft and miles). So, I changed const geodesicLength = geodeticLengthOperator.execute(line, { units: "kilometers" }); const planarLength = lengthOperator.execute(line, { units: "kilometers" }); const geodesicArea = geodeticAreaOperator.execute(polygon, { units: "square-kilometers" }); const planarArea = areaOperator.execute(polygon, { units: "square-kilometers" }); to: const geodesicLength = geodeticLengthOperator.execute(line, { units: "miles" }); const planarLength = lengthOperator.execute(line, { units: "feet" }); const geodesicArea = geodeticAreaOperator.execute(polygon, { units: "square-miles" }); const planarArea = areaOperator.execute(polygon, { units: "square-feet" }); Then I noticed that the geodetic measurements were way off incorrect Then I changed the "units" to "unit" for geodetic measurements  const geodesicLength = geodeticLengthOperator.execute(line, { unit: "miles" }); const planarLength = lengthOperator.execute(line, { units: "feet" }); const geodesicArea = geodeticAreaOperator.execute(polygon, { unit: "square-miles" }); const planarArea = areaOperator.execute(polygon, { units: "square-feet" });   and now I get correct results!! I don't see anywhere in the documentation stating to use unit instead of units for geodetic measurements.     ... View more