<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Problem with deriving from built-in widgets which does not support generics in ArcGIS Online Developers Questions</title>
    <link>https://community.esri.com/t5/arcgis-online-developers-questions/problem-with-deriving-from-built-in-widgets-which/m-p/1280196#M1223</link>
    <description>&lt;P&gt;Trying to derive from built-in widgets to add custom functionalities or workarounds.&lt;/P&gt;&lt;P&gt;For the most part been successful with it, but there is one issue came across:&lt;/P&gt;&lt;P&gt;for e.g.&lt;/P&gt;&lt;P&gt;doing something like:&lt;/P&gt;&lt;P&gt;import Edit from '../../../../../dist/widgets/common/edit/src/runtime/widget';&lt;/P&gt;&lt;P&gt;export default class Widget extends Edit { ... }&lt;BR /&gt;&lt;BR /&gt;but the base class does not support generics, so currently there doesn't seem to be a way to add to (modify) the base class state or property interfaces, which are being used in the base classes...&lt;/P&gt;&lt;P&gt;Need to add fields to persisted state properties from settings that will get persisted to the widget during runtime, in child setting/widget classes that derive from base built-in widgets...&lt;BR /&gt;&lt;BR /&gt;Is there way of inheriting from the base built-in classes (both for the Widget and Setting classes) to accomplish this?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 19 Apr 2023 15:51:13 GMT</pubDate>
    <dc:creator>Gurunara</dc:creator>
    <dc:date>2023-04-19T15:51:13Z</dc:date>
    <item>
      <title>Problem with deriving from built-in widgets which does not support generics</title>
      <link>https://community.esri.com/t5/arcgis-online-developers-questions/problem-with-deriving-from-built-in-widgets-which/m-p/1280196#M1223</link>
      <description>&lt;P&gt;Trying to derive from built-in widgets to add custom functionalities or workarounds.&lt;/P&gt;&lt;P&gt;For the most part been successful with it, but there is one issue came across:&lt;/P&gt;&lt;P&gt;for e.g.&lt;/P&gt;&lt;P&gt;doing something like:&lt;/P&gt;&lt;P&gt;import Edit from '../../../../../dist/widgets/common/edit/src/runtime/widget';&lt;/P&gt;&lt;P&gt;export default class Widget extends Edit { ... }&lt;BR /&gt;&lt;BR /&gt;but the base class does not support generics, so currently there doesn't seem to be a way to add to (modify) the base class state or property interfaces, which are being used in the base classes...&lt;/P&gt;&lt;P&gt;Need to add fields to persisted state properties from settings that will get persisted to the widget during runtime, in child setting/widget classes that derive from base built-in widgets...&lt;BR /&gt;&lt;BR /&gt;Is there way of inheriting from the base built-in classes (both for the Widget and Setting classes) to accomplish this?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Apr 2023 15:51:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-developers-questions/problem-with-deriving-from-built-in-widgets-which/m-p/1280196#M1223</guid>
      <dc:creator>Gurunara</dc:creator>
      <dc:date>2023-04-19T15:51:13Z</dc:date>
    </item>
  </channel>
</rss>

