@oracle/oraclejet-core-pack 16.1.4 → 17.0.0

package/oj-c/TextArea.json

@@ -6,7 +6,7 @@
     "memberof": "oj-c",
     "longname": "oj-c.TextArea",
     "kind": "class",
-    "classdesc": "<h3 id=\"textAreaOverview-section\">\n  JET TextArea Component\n  <a class=\"bookmarkable-link\" title=\"Bookmarkable Link\" href=\"#textAreaOverview-section\"></a>\n</h3>\n\n<p>Description: The oj-c-text-area component enhances a browser textarea element.</p>\n\n<pre class=\"prettyprint\"><code>&lt;oj-c-text-area value=\"value text\">&lt;/oj-c-text-area></code></pre>\n\n<h3 id=\"validation-section\">\n  Validation and Messaging\n  <a class=\"bookmarkable-link\" title=\"Bookmarkable Link\" href=\"#validation-section\"></a>\n</h3>\n\n<p>\nAn editable component runs validation (normal or deferred) based on the action performed on it\n(either by end-user or page author), and the state it was in when the action occurred. Examples\nof actions are - creating a component, user changing the value of the component by interacting\nwith it, the app setting a value programmatically, the app calling the validate() method etc. At\nthe time the action occurs, the component could already be showing errors, or can have a deferred\nerror or have no errors.\n</p>\n<p>\nThese factors also determine whether validation errors/messages get shown to the user immediately\nor get deferred. The following sections highlight the kinds of validation that are run and how\nmessages get handled.\n</p>\n\n<h4 id=\"normal-validation-section\">\n  Normal Validation\n  <a class=\"bookmarkable-link\" title=\"Bookmarkable Link\" href=\"#normal-validation-section\"></a>\n</h4>\nNormal validation is run in the following cases on the display value, using the converter and\nvalidators (this includes async-validators) set on the component,\nand validation errors are reported to user immediately.\n<ul>\n<li>When value changes as a result of user interaction all messages are cleared, including custom\nmessages added by the app, and full validation is run on the UI value. The steps performed are\noutlined below.\n<ol>\n<li>All messages are cleared and <code class=\"prettyprint\">messagesCustom</code> property is cleared</li>\n<li>If no converter is present then processing continues to next step. If a converter is\npresent, the UI value is first converted (i.e., parsed). If there is a parse error then\nthe messages are shown and processing returns.</li>\n<li>If there are no validators setup for the component then the value is set on the component.\nOtherwise all validators are run in sequence using the parsed value from the previous step. The\nimplicit required is run first if the component is marked required. When a validation error is\nencountered it is remembered and the next validator in the sequence is run.\n<ul><li>NOTE: The value is trimmed before required validation is run</li></ul>\n</li>\n<li>At the end of the validation run if there are errors, the messages are shown\nand processing returns. If there are async-validators, those errors are shown as soon as they\ncome in, and not until all validators, sync and async validators, are complete, does processing\nreturn, that is, value and valid are updated. If there are no errors, then the\n<code class=\"prettyprint\">value</code> property is updated and the formatted value displayed on the\nUI.</li>\n</ol>\n</li>\n<li>When the <code class=\"prettyprint\">validate</code> method is called by app, all messages are\ncleared and full validation run using the display value. See <code class=\"prettyprint\">validate</code>\nmethod on the sub-classes for details. Note: JET validation is designed to catch user input errors, and not invalid\ndata passed from the server; this should be caught on the server.</li>\n<li>When certain properties change through programmatic intervention by app, the component\ndetermines whether it needs to run normal validation based on the state the component is in.\nRefer to the <a href=\"#mixed-validation-section\">Mixed Validation</a> section below for details. </li>\n</ul>\n\n<h4 id=\"deferred-validation-section\">\n  Deferred Validation\n  <a class=\"bookmarkable-link\" title=\"Bookmarkable Link\" href=\"#deferred-validation-section\"></a>\n</h4>\nDeferred validation is run in the following cases on the component value using the implicit\nrequired validator if required is true, and validation errors are deferred, i.e., not shown to user immediately.\nRefer to the <a href=\"#deferred-messages-section\">Showing Deferred Messages</a> section to\nunderstand how deferred messages can be shown.\n<ul>\n <li>When a component is created and it is required deferred validation is run and no messages are cleared\n prior to running validation.\n Refer to the <a href=\"#deferred-validators-section\">Validators\n Participating in Deferred Validation</a> section for details.</li>\n <li>When the <code class=\"prettyprint\">value</code> property changes due to programmatic\n intervention deferred validation is run, after all messages and messagesCustom property are cleared.</li>\n <li>When the <code class=\"prettyprint\">reset</code> method is called, deferred validation is run\n  after all messages and messagesCustom property are cleared.</li>\n <li>When certain properties change through programmatic intervention by app, the component\n determines whether it needs to run deferred validation based on the state the component is in.\n Refer to the <a href=\"#mixed-validation-section\">Mixed Validation</a> section below for details.</li>\n</ul>\n\n<h4 id=\"mixed-validation-section\">\n  Mixed Validation\n  <a class=\"bookmarkable-link\" title=\"Bookmarkable Link\" href=\"#mixed-validation-section\"></a>\n</h4>\nEither deferred or normal validation is run in the following cases based on the state the\ncomponent is in and any validation errors encountered are either hidden or shown to user.\n<ul>\n <li>when disabled property changes. See <a href=\"#disabled\">disabled</a> property for details.</li>\n <li>when converter property changes. See <a href=\"#converter\">converter</a> property for details.</li>\n <li>when required property changes. See <a href=\"#required\">required</a> property for details.</li>\n <li>when validators property changes. See <a href=\"#validators\">validators</a> property for details.</li>\n</ul>\n\n<h3 id=\"deferred-messages-section\">\n  Showing Deferred Messages\n  <a class=\"bookmarkable-link\" title=\"Bookmarkable Link\" href=\"#deferred-messages-section\"></a>\n</h3>\nDeferred validation messages are displayed only when page author requests for it explicitly in\none of the following ways:\n<ul>\n<li>calls the <a href=\"#showMessages\"><code class=\"prettyprint\">showMessages</code></a> method on the component</li>\n</ul>\n\n<h3 id=\"deferred-validators-section\">\n  Validators Participating in Deferred Validation\n  <a class=\"bookmarkable-link\" title=\"Bookmarkable Link\" href=\"#deferred-validators-section\"></a>\n</h3>\nThe required validator is the only validator type that participates in deferred validation.\nThe required property needs to be set to true for the required validator to run.\n\n<h3 id=\"user-assistance-text-section\">\n  User Assistance Text\n  <a class=\"bookmarkable-link\" title=\"Bookmarkable Link\" href=\"#user-assistance-text-section\"></a>\n</h3>\n<p>\nUser assistive text provides guidance to help the user understand what data to enter or select.\n</p>\n<p>\nBy default all user assistance text shows inline.\nFor input components, it shows when the field takes focus. In other components\nit shows all the time. See the user-assistance-density property for other ways\nthe user assistance text can render, like in 'compact' mode, it will render as an icon on the label\nwhich when clicked will show the user assistance text in a notewindow.\n</p>\n<p>\nThe JET form component properties that are used for user assistance text are help.instruction,\nvalidator and converter hints, and help-hints.\nIn the Redwood theme for clarity only one user assistance text shows to the user.\nThe precedence rules are:\n<ul>\n<li>help.instruction shows;</li>\n<li>if no help.instruction, then validator hint shows;</li>\n<li>if no help.instruction or validator hint, then help-hints.definition shows;</li>\n<li>if no help.instruction, validator hint, or help-hints.definition, then converter hint shows.</li>\n<li>help-hints.source always shows along side the above.</li>\n</ul>\n</p>\n<p>Sometimes a validator or converter hint shows that you do not want to show. To not show it,\n set the display-options.validator-hint and/or display-options.converter-hint property to 'none'.\n</p>\n<p>required and placeholder properties also can be used to guide the user.\nIn Redwood, a required field shows the word Required under the field\nwhen the field is empty and does not have focus.\nPlaceholder is shown when the field is empty and has focus.\n</p>\n\n<h3 id=\"touch-section\">\n  Touch End User Information\n  <a class=\"bookmarkable-link\" title=\"Bookmarkable Link\" href=\"#touch-section\"></a>\n</h3>\n\n<table class=\"keyboard-table\">\n  <thead>\n    <tr>\n      <th>Target</th>\n      <th>Gesture</th>\n      <th>Action</th>\n    </tr>\n  </thead>\n  <tbody>\n    <tr>\n      <td>Input</td>\n      <td><kbd>Tap</kbd></td>\n      <td>Sets focus to input. Show user assistance text.</td>\n    </tr>\n  </tbody>\n</table>\n\n<h3 id=\"keyboard-section\">\n  Keyboard End User Information\n  <a class=\"bookmarkable-link\" title=\"Bookmarkable Link\" href=\"#keyboard-section\"></a>\n</h3>\n\n<table class=\"keyboard-table\">\n  <thead>\n    <tr>\n      <th>Target</th>\n      <th>Key</th>\n      <th>Action</th>\n    </tr>\n  </thead>\n  <tbody>\n    <tr>\n      <td>Input</td>\n      <td><kbd>Tab In</kbd></td>\n      <td>Set focus to the input. Show user assistance text.</td>\n    </tr>\n  </tbody>\n</table>\n\n<h3 id=\"a11y-section\">\n  Accessibility\n  <a class=\"bookmarkable-link\" title=\"Bookmarkable Link\" href=\"#a11y-section\"></a>\n</h3>\n\n<p>\nFor accessibility, set the <a href=\"#labelHint\">label-hint</a> property.\nIf there is no visible label, then to make this accessible to screen reader users,\nset the <a href=\"#labelHint\">label-hint</a> and <a href=\"#labelEdge\">label-edge</a>='none'\nwhich renders an aria-label with the label-hint text.\n</p>\n\n<p>\nThe placeholder text is not read reliably by the screen reader. For accessibility reasons,\nyou need to associate the text to its JET form component using aria-describedby.\n</p>\n\n<p>\nDisabled content: JET supports an accessible luminosity contrast ratio,\nas specified in <a href=\"http://www.w3.org/TR/WCAG20/#visual-audio-contrast-contrast\">WCAG 2.0 - Section 1.4.3 \"Contrast\"</a>,\nin the themes that are accessible.  (See the \"Theming\" chapter of the JET Developer Guide for more information on which\nthemes are accessible.)  Note that Section 1.4.3 says that text or images of text that are part of an inactive user\ninterface component have no contrast requirement.  Because disabled content may not meet the minimum contrast ratio\nrequired of enabled content, it cannot be used to convey meaningful information.\n</p>",
+    "classdesc": "<h3 id=\"textAreaOverview-section\">\n  JET TextArea Component\n  <a class=\"bookmarkable-link\" title=\"Bookmarkable Link\" href=\"#textAreaOverview-section\"></a>\n</h3>\n\n<p>Description: The oj-c-text-area component enhances a browser textarea element.</p>\n\n<pre class=\"prettyprint\"><code>&lt;oj-c-text-area value=\"value text\">&lt;/oj-c-text-area></code></pre>\n\n<h3 id=\"validation-section\">\n  Validation and Messaging\n  <a class=\"bookmarkable-link\" title=\"Bookmarkable Link\" href=\"#validation-section\"></a>\n</h3>\n\n<p>\nAn editable component runs validation (normal or deferred) based on the action performed on it\n(either by end-user or page author), and the state it was in when the action occurred. Examples\nof actions are - creating a component, user changing the value of the component by interacting\nwith it, the app setting a value programmatically, the app calling the validate() method etc. At\nthe time the action occurs, the component could already be showing errors, or can have a deferred\nerror or have no errors.\n</p>\n<p>\nThese factors also determine whether validation errors/messages get shown to the user immediately\nor get deferred. The following sections highlight the kinds of validation that are run and how\nmessages get handled.\n</p>\n\n<h4 id=\"normal-validation-section\">\n  Normal Validation\n  <a class=\"bookmarkable-link\" title=\"Bookmarkable Link\" href=\"#normal-validation-section\"></a>\n</h4>\nNormal validation is run in the following cases on the display value, using the converter and\nvalidators (this includes async-validators) set on the component,\nand validation errors are reported to user immediately.\n<ul>\n<li>When value changes as a result of user interaction all messages are cleared, including custom\nmessages added by the app, and full validation is run on the UI value. The steps performed are\noutlined below.\n<ol>\n<li>All messages are cleared and <code class=\"prettyprint\">messagesCustom</code> property is cleared</li>\n<li>If no converter is present then processing continues to next step. If a converter is\npresent, the UI value is first converted (i.e., parsed). If there is a parse error then\nthe messages are shown and processing returns.</li>\n<li>If there are no validators setup for the component then the value is set on the component.\nOtherwise all validators are run in sequence using the parsed value from the previous step. The\nimplicit required is run first if the component is marked required. When a validation error is\nencountered it is remembered and the next validator in the sequence is run.\n<ul><li>NOTE: The value is trimmed before required validation is run</li></ul>\n</li>\n<li>At the end of the validation run if there are errors, the messages are shown\nand processing returns. If there are async-validators, those errors are shown as soon as they\ncome in, and not until all validators, sync and async validators, are complete, does processing\nreturn, that is, value and valid are updated. If there are no errors, then the\n<code class=\"prettyprint\">value</code> property is updated and the formatted value displayed on the\nUI.</li>\n</ol>\n</li>\n<li>When the <code class=\"prettyprint\">validate</code> method is called by app, all messages are\ncleared and full validation run using the display value. See <code class=\"prettyprint\">validate</code>\nmethod on the sub-classes for details. Note: JET validation is designed to catch user input errors, and not invalid\ndata passed from the server; this should be caught on the server.</li>\n<li>When certain properties change through programmatic intervention by app, the component\ndetermines whether it needs to run normal validation based on the state the component is in.\nRefer to the <a href=\"#mixed-validation-section\">Mixed Validation</a> section below for details. </li>\n</ul>\n\n<h4 id=\"deferred-validation-section\">\n  Deferred Validation\n  <a class=\"bookmarkable-link\" title=\"Bookmarkable Link\" href=\"#deferred-validation-section\"></a>\n</h4>\nDeferred validation is run in the following cases on the component value using the implicit\nrequired validator if required is true, and validation errors are deferred, i.e., not shown to user immediately.\nRefer to the <a href=\"#deferred-messages-section\">Showing Deferred Messages</a> section to\nunderstand how deferred messages can be shown.\n<ul>\n <li>When a component is created and it is required deferred validation is run and no messages are cleared\n prior to running validation.\n Refer to the <a href=\"#deferred-validators-section\">Validators\n Participating in Deferred Validation</a> section for details.</li>\n <li>When the <code class=\"prettyprint\">value</code> property changes due to programmatic\n intervention deferred validation is run, after all messages and messagesCustom property are cleared.</li>\n <li>When the <code class=\"prettyprint\">reset</code> method is called, deferred validation is run\n  after all messages and messagesCustom property are cleared.</li>\n <li>When certain properties change through programmatic intervention by app, the component\n determines whether it needs to run deferred validation based on the state the component is in.\n Refer to the <a href=\"#mixed-validation-section\">Mixed Validation</a> section below for details.</li>\n</ul>\n\n<h4 id=\"mixed-validation-section\">\n  Mixed Validation\n  <a class=\"bookmarkable-link\" title=\"Bookmarkable Link\" href=\"#mixed-validation-section\"></a>\n</h4>\nEither deferred or normal validation is run in the following cases based on the state the\ncomponent is in and any validation errors encountered are either hidden or shown to user.\n<ul>\n <li>when disabled property changes. See <a href=\"#disabled\">disabled</a> property for details.</li>\n <li>when converter property changes. See <a href=\"#converter\">converter</a> property for details.</li>\n <li>when required property changes. See <a href=\"#required\">required</a> property for details.</li>\n <li>when validators property changes. See <a href=\"#validators\">validators</a> property for details.</li>\n</ul>\n\n<h3 id=\"deferred-messages-section\">\n  Showing Deferred Messages\n  <a class=\"bookmarkable-link\" title=\"Bookmarkable Link\" href=\"#deferred-messages-section\"></a>\n</h3>\nDeferred validation messages are displayed only when page author requests for it explicitly in\none of the following ways:\n<ul>\n<li>calls the <a href=\"#showMessages\"><code class=\"prettyprint\">showMessages</code></a> method on the component</li>\n</ul>\n\n<h3 id=\"deferred-validators-section\">\n  Validators Participating in Deferred Validation\n  <a class=\"bookmarkable-link\" title=\"Bookmarkable Link\" href=\"#deferred-validators-section\"></a>\n</h3>\nThe required validator is the only validator type that participates in deferred validation.\nThe required property needs to be set to true for the required validator to run.\n\n<h3 id=\"user-assistance-text-section\">\n  User Assistance Text\n  <a class=\"bookmarkable-link\" title=\"Bookmarkable Link\" href=\"#user-assistance-text-section\"></a>\n</h3>\n<p>\nUser assistive text provides guidance to help the user understand what data to enter or select.\n</p>\n<p>\nBy default all user assistance text shows inline.\nFor input components, it shows when the field takes focus. In other components\nit shows all the time. See the user-assistance-density property for other ways\nthe user assistance text can render, like in 'compact' mode, it will render as an icon on the label\nwhich when clicked will show the user assistance text in a notewindow.\n</p>\n<p>\nThe JET form component properties that are used for user assistance text are help.instruction,\nvalidator and converter hints, and help-hints.\nIn the Redwood theme for clarity only one user assistance text shows to the user.\nThe precedence rules are:\n<ul>\n<li>help.instruction shows;</li>\n<li>if no help.instruction, then validator hint shows;</li>\n<li>if no help.instruction or validator hint, then help-hints.definition shows;</li>\n<li>if no help.instruction, validator hint, or help-hints.definition, then converter hint shows.</li>\n<li>help-hints.source always shows along side the above.</li>\n</ul>\n</p>\n<p>Sometimes a validator or converter hint shows that you do not want to show. To not show it,\n set the display-options.validator-hint and/or display-options.converter-hint property to 'none'.\n</p>\n<p>The required and placeholder properties also can be used to guide the user.\nIn Redwood, a required field shows the word Required under the field\nwhen the field is empty and does not have focus.\nPlaceholder is shown when the field is empty and has focus.\n</p>\n\n<h3 id=\"touch-section\">\n  Touch End User Information\n  <a class=\"bookmarkable-link\" title=\"Bookmarkable Link\" href=\"#touch-section\"></a>\n</h3>\n\n<table class=\"keyboard-table\">\n  <thead>\n    <tr>\n      <th>Target</th>\n      <th>Gesture</th>\n      <th>Action</th>\n    </tr>\n  </thead>\n  <tbody>\n    <tr>\n      <td>Input</td>\n      <td><kbd>Tap</kbd></td>\n      <td>Sets focus to input. Show user assistance text.</td>\n    </tr>\n  </tbody>\n</table>\n\n<h3 id=\"keyboard-section\">\n  Keyboard End User Information\n  <a class=\"bookmarkable-link\" title=\"Bookmarkable Link\" href=\"#keyboard-section\"></a>\n</h3>\n\n<table class=\"keyboard-table\">\n  <thead>\n    <tr>\n      <th>Target</th>\n      <th>Key</th>\n      <th>Action</th>\n    </tr>\n  </thead>\n  <tbody>\n    <tr>\n      <td>Input</td>\n      <td><kbd>Tab In</kbd></td>\n      <td>Set focus to the input. Show user assistance text.</td>\n    </tr>\n  </tbody>\n</table>\n\n<h3 id=\"a11y-section\">\n  Accessibility\n  <a class=\"bookmarkable-link\" title=\"Bookmarkable Link\" href=\"#a11y-section\"></a>\n</h3>\n\n<p>\nFor accessibility, set the <a href=\"#labelHint\">label-hint</a> property.\nIf there is no visible label, then to make this accessible to screen reader users,\nset the <a href=\"#labelHint\">label-hint</a> and <a href=\"#labelEdge\">label-edge</a>='none'\nwhich renders an aria-label with the label-hint text.\n</p>\n\n<p>\nThe placeholder text is not read reliably by the screen reader. For accessibility reasons,\nyou need to associate the text to its JET form component using aria-describedby.\n</p>\n\n<p>\nDisabled content: JET supports an accessible luminosity contrast ratio,\nas specified in <a href=\"http://www.w3.org/TR/WCAG20/#visual-audio-contrast-contrast\">WCAG 2.0 - Section 1.4.3 \"Contrast\"</a>,\nin the themes that are accessible.  (See the \"Theming\" chapter of the JET Developer Guide for more information on which\nthemes are accessible.)  Note that Section 1.4.3 says that text or images of text that are part of an inactive user\ninterface component have no contrast requirement.  Because disabled content may not meet the minimum contrast ratio\nrequired of enabled content, it cannot be used to convey meaningful information.\n</p>",
     "scope": "static",
     "tagWithoutBrackets": "oj-c-text-area",
     "tagWithBrackets": "<oj-c-text-area>",
@@ -39,7 +39,7 @@
     ],
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "ojmodule": "text-area"
   },
@@ -54,7 +54,7 @@
     "description": "Dictates component's autocomplete state. This attribute indicates whether the value of\nthe control can be automatically completed by the browser. The common values are 'on' and 'off'.\n\nSince this attribute passes through to the textarea element unchanged, you can look at the html specs for\ndetailed information for how browsers behave and what values besides 'on' and 'off' you can set.\nThe html spec says the default is 'on', so when autocomplete is not explicitly set, the browsers treat it as 'on'.",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "defaultvalue": "\"on\"",
     "type": {
@@ -74,7 +74,7 @@
     "description": "Specifies how many columns this component should span.\nThis only takes effect when this component is a child of a form layout\nthat has direction 'row'.",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "defaultvalue": 1,
     "type": {
@@ -94,7 +94,7 @@
     "description": "Specifies whether an ancestor container, like oj-c-form-layout, is readonly.\nThis affects whether a readonly component renders in full or mixed readonly mode.\nThis is also currently used to determine if there is an ancestor container by checking if the value\nis not equal to undefined.",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "type": {
       "names": [
@@ -113,21 +113,14 @@
     "description": "A converter instance or one that duck types oj.Converter.\n<p>\nWhen <code class=\"prettyprint\">converter</code> property changes due to programmatic\nintervention, the element performs various tasks based on the current state it is in. </br>\n\n<h4>Steps Performed Always</h4>\n<ul>\n<li>Any cached converter instance is cleared and new converter created. The converter hint is\npushed to messaging. E.g., notewindow displays the new hint(s).\n</li>\n</ul>\n\n<h4>Running Validation</h4>\n<ul>\n<li>if element is valid when <code class=\"prettyprint\">converter</code> property changes, the\n display value is refreshed.</li>\n<li>if element is invalid and is showing messages when\n<code class=\"prettyprint\">converter</code> property changes then all element messages are\ncleared and full validation run using the current display value on the element.\n<ul>\n  <li>if there are validation errors, then <code class=\"prettyprint\">value</code>\n  property is not updated, and the error is shown.\n  The display value is not refreshed in this case. </li>\n  <li>if no errors result from the validation, the <code class=\"prettyprint\">value</code>\n  property is updated; page author can listen to the <code class=\"prettyprint\">valueChanged</code>\n  event to clear custom errors. The\n  display value is refreshed with the formatted value provided by converter.</li>\n</ul>\n</li>\n<li>if element is invalid and has deferred messages when converter property changes, the\n  display value is again refreshed with the formatted value provided by converter.</li>\n</ul>\n\n<h4>Clearing Messages</h4>\n<ul>\n<li>Only messages created by the element are cleared.</li>\n<li><code class=\"prettyprint\">messagesCustom</code> property is not cleared.\nPage authors can\nchoose to clear it explicitly when setting the converter option.</li>\n</ul>\n</p>\n<p>\n During validation, the converter takes the input value which is a string\n and parses it into the type of the component's value property\n (e.g. a number)\n before it passes it to the validator. It then takes the validated value property\n and formats it into a string to be displayed and puts it into the input.\n If the converter's format or parse functions\n throw an error, it will be displayed to the user inline on the field.\n</p>\n<p>\nThe hint exposed by the converter is shown inline by default in the Redwood theme when\nthe field has focus.\nYou can turn off showing converter hints by using the\n'converterHint' property set to 'none' on the <code class=\"prettyprint\">display-options</code>\nattribute.\n</p>\n<p>\nIn the Redwood theme, only one hint shows at a time, so the precedence rules are:\nhelp.instruction shows; if no help.instruction then validator hints show;\nif none, then help-hints.definition shows; if none, then converter hint shows.\nhelp-hints.source always shows along with the other help or hint.\n</p>",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "defaultvalue": null,
     "type": {
       "names": [
         "object|null"
       ]
-    },
-    "tstype": [
-      {
-        "target": "Type",
-        "value": "Converter<V>|null",
-        "jsdocOverride": true
-      }
-    ]
+    }
   },
   {
     "memberof": "oj-c.TextArea",
@@ -140,7 +133,7 @@
     "description": "Whether the component is disabled. The default is false.\n\n<p>\nWhen the <code class=\"prettyprint\">disabled</code> property changes due to programmatic\nintervention, the component may clear messages and run validation in some cases. </br>\n<ul>\n<li>when a required component is initialized as disabled\n<code class=\"prettyprint\">value=\"{{currentValue}}\" required disabled</code>,\ndeferred validation is skipped.</li>\n<li>when a disabled component is enabled,\n <ul>\n <li>if component is invalid and showing messages then all component messages are cleared,\n and full validation run using the display value.\n  <ul>\n   <li>if there are validation errors, they are shown.</li>\n   <li>if no errors result from the validation, the <code class=\"prettyprint\">value</code>\n   property is updated. Page authors can listen to the <code class=\"prettyprint\">valueChanged</code>\n   event to clear custom errors.</li>\n  </ul>\n </li>\n\n <li>if component is valid and has no errors then deferred validation is run.\n   <ul>\n   <li>if there is a deferred validation error, then the valid property is updated. </li>\n   </ul>\n </li>\n <li>if component is invalid and deferred errors then component messages are cleared and\n deferred validation re-run.\n   <ul>\n   <li>if there is a deferred validation error, then the valid property is updated.</li>\n   </ul>\n </li>\n </ul>\n</li>\n<li>when enabled component is disabled then no validation is run and the component appears\ndisabled.</li>\n</ul>\n</p>",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "defaultvalue": false,
     "type": {
@@ -160,7 +153,7 @@
     "description": "Display options for auxiliary content that determines whether or not it should be displayed.",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "type": {
       "names": [
@@ -186,7 +179,7 @@
     "description": "Form component help information.",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "type": {
       "names": [
@@ -212,7 +205,7 @@
     "description": "The helpHints object contains a definition property and a source property.",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "type": {
       "names": [
@@ -238,7 +231,7 @@
     "description": "Specifies how the label of the component is positioned when the label-hint\nattribute is set on the component.",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "ojvalues": [
       {
@@ -302,7 +295,7 @@
     "description": "Represents a hint for rendering a label on the component.\nThis is used in combination with the label-edge attribute to control how the label should be rendered.",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "type": {
       "names": [
@@ -321,20 +314,13 @@
     "description": "<p> The width of the label when labelEdge is 'start'.</p>\n<p> This attribute accepts values of type\n<code>0 | `--${string}` | `${number}%` | `${number}x` | `calc(${string})`</code></p>",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "type": {
       "names": [
         "number|string"
       ]
-    },
-    "tstype": [
-      {
-        "target": "Type",
-        "value": "Size",
-        "jsdocOverride": true
-      }
-    ]
+    }
   },
   {
     "memberof": "oj-c.TextArea",
@@ -347,7 +333,7 @@
     "description": "Should the labels wrap or truncate when there is not enough available space.",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "ojvalues": [
       {
@@ -389,7 +375,7 @@
     "description": "Defines the length limit for the field",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "type": {
       "names": [
@@ -415,7 +401,7 @@
     "description": "The maximum number of visible text lines of the textarea. The textarea will change its height in\nresponse to content change. If this is 0, the number of visible text lines is always as specified\nby the \"rows\" attribute, and the textarea will never change its size. If this is -1, there is no\nmaximum and the textarea will grow to show all the content. If this is a positive number larger\nthan the \"rows\" attribute, the textarea will grow to fit the content, up to the maximum number of\ntext lines. The height will never be less than the number of rows specified by the \"rows\" attribute.",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "type": {
       "names": [
@@ -435,7 +421,7 @@
     "description": "List of messages an app would add to the component when it has business/custom validation\nerrors that it wants the component to show. This allows the app to perform further validation\nbefore sending data to the server. When this option is set the message shows to the\nuser right away. To clear the custom message, set <code class=\"prettyprint\">messagesCustom</code>\nback to an empty array.<br/>\n<p>\nSee the <a href=\"#validation-section\">Validation and Messages</a> section\nfor details on when the component clears <code class=\"prettyprint\">messagesCustom</code>;\nfor example, when full validation is run.\n</p>",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "defaultvalue": "[]",
     "type": {
@@ -462,7 +448,7 @@
     "description": "The placeholder text to set on the element.",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "type": {
       "names": [
@@ -478,12 +464,11 @@
     "longname": "oj-c.TextArea#readonly",
     "optional": true,
     "scope": "instance",
-    "description": "Whether the component is readonly. The readonly property sets or returns whether an element\nis readonly, or not. A readonly element cannot be modified. However, a user can tab to it,\nhighlight it, focus on it, and copy the text from it. If you want to prevent the user from\ninteracting with the element, use the disabled property instead.",
+    "description": "<p>\nWhether the component is readonly. The readonly property sets or returns whether an element\nis readonly, or not. A readonly element cannot be modified. However, a user can tab to it,\nhighlight it, focus on it, and copy the text from it. If you want to prevent the user from\ninteracting with the element, use the disabled property instead.\n</p>\n<p>\nIf the property value is not set either directly on the component or inherited from\na parent form layout, then the property is treated as if its value were false.\n</p>",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
-    "defaultvalue": false,
     "type": {
       "names": [
         "boolean"
@@ -501,7 +486,7 @@
     "description": "<p>\nThis property set to <code class=\"prettyprint\">false</code> implies that a value is not required to be provided by the user.\nThis is the default.\nThis property set to <code class=\"prettyprint\">true</code> implies that a value is required to be provided by the user.\n</p>\n<p>\nIn the Redwood theme, by default, a Required text is rendered inline when the field is empty.\nIf user-assistance-density is 'compact', it will show on the label as an icon.\n</p>\n<p>The Required error text is based on Redwood UX designs, and it is not recommended that\nit be changed.\nTo override the required error message,\nuse the <code class=\"prettyprint\">required-message-detail</code> attribute.\nThe component's label text is passed in as a token {label} and can be used in the message detail.\n</p>\n<p>When required is set to true, an implicit\nrequired validator is created, i.e.,\n<code class=\"prettyprint\">new RequiredValidator()</code>. The required validator is the only\nvalidator to run during initial render, and its error is not shown to the user at this time;\nthis is called deferred validation. The required validator also runs during normal validation;\nthis is when the errors are shown to the user.\nSee the <a href=\"#validation-section\">Validation and Messaging</a> section for details.\n</p>\n<p>\nWhen the <code class=\"prettyprint\">required</code> property changes due to programmatic intervention,\nthe component may clear component messages and run validation, based on the current state it's in. </br>\n\n<h4>Running Validation when required property changes</h4>\n<ul>\n<li>if component is valid when required is set to true, then it runs deferred validation on\nthe value property. If the field is empty, the valid state is invalidHidden. No errors are\nshown to the user.\n</li>\n<li>if component is valid when required is set from true to false, then no validation is run.\n</li>\n<li>if component is invalid and has deferred messages when required is set to false, then\ncomponent messages are cleared (messages-custom messages are not cleared)\nbut no deferred validation is run because required is false.\n</li>\n<li>if component is invalid and currently showing invalid messages (invalidShown) when required is changed\nto either true or false, then\ncomponent messages are cleared and normal validation is run using the current display value.\n<ul>\n  <li>if there are validation errors, then <code class=\"prettyprint\">value</code>\n  property is not updated and the error is shown.\n  </li>\n  <li>if no errors result from the validation, the <code class=\"prettyprint\">value</code>\n  property is updated; page author can listen to the <code class=\"prettyprint\">valueChanged</code>\n  event on the component to clear custom errors.</li>\n</ul>\n</li>\n</ul>\n\n<h4>Clearing Messages when required property changes</h4>\n<ul>\n<li>Only messages created by the component, like validation messages, are cleared when the required property changes.</li>\n<li><code class=\"prettyprint\">messagesCustom</code> property is not cleared.</li>\n</ul>\n\n</p>",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "defaultvalue": false,
     "type": {
@@ -521,7 +506,7 @@
     "description": "<p>\nThe component-specific message detail when the required validation fails.\nIf the component needs a required validation error message that is different from the default,\nset this property. It should be a translated string.\n</p>",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "type": {
       "names": [
@@ -540,7 +525,7 @@
     "description": "Defines the resizeBehavior of the textarea. Note that this is implemented via the native browser support\nfor resize on the textarea element. If a browser doesn't support this (IE, Edge, iOS, Android), then\nthis attribute has no effect.",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "ojvalues": [
       {
@@ -602,10 +587,10 @@
     "longname": "oj-c.TextArea#rows",
     "optional": true,
     "scope": "instance",
-    "description": "The number of visible text lines in the textarea. It can also be used to give specific height to the\ntextarea. When used in conjuction with max-rows, the rows attribnute will be the minimum height of\nthe textarea.",
+    "description": "The number of visible text lines in the textarea. It can also be used to give specific height to the\ntextarea. When used in conjuction with max-rows, the rows attribute will be the minimum height of\nthe textarea.",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "type": {
       "names": [
@@ -624,7 +609,7 @@
     "description": "Specifies how the text is aligned within the text field",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "ojvalues": [
       {
@@ -666,26 +651,6 @@
       ]
     }
   },
-  {
-    "memberof": "oj-c.TextArea",
-    "id": "oj-c.TextArea#unsafe_labelledBy",
-    "name": "unsafe_labelledBy",
-    "kind": "member",
-    "longname": "oj-c.TextArea#unsafe_labelledBy",
-    "optional": true,
-    "scope": "instance",
-    "description": "This is temporary unsafe API for JET-52089. It enables a wrapper VComponent to pass\nthe id of an external label that it wants to associate with the inner input.",
-    "ojhidden": true,
-    "meta": {
-      "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
-    },
-    "type": {
-      "names": [
-        "string"
-      ]
-    }
-  },
   {
     "memberof": "oj-c.TextArea",
     "id": "oj-c.TextArea#userAssistanceDensity",
@@ -694,10 +659,10 @@
     "longname": "oj-c.TextArea#userAssistanceDensity",
     "optional": true,
     "scope": "instance",
-    "description": "Specifies the density of the form component's user assistance presentation. It can be shown inline with\nreserved rows to prevent reflow if a user assistance text shows up, inline without reserved rows that would\nreflow if a user assistance text shows up, or it can be shown compactly in a popup instead.",
+    "description": "<p>\nSpecifies the density of the form component's user assistance presentation. It can be shown inline with\nreserved rows to prevent reflow if a user assistance text shows up, inline without reserved rows that would\nreflow if a user assistance text shows up, or it can be shown compactly in a popup instead.\n</p>\n<p>\nIf the property value is not set either directly on the component or inherited from\na parent form layout, then the property is treated as if its value were \"reflow\".\n</p>",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "ojvalues": [
       {
@@ -731,7 +696,6 @@
         }
       }
     ],
-    "defaultvalue": "\"reflow\"",
     "type": {
       "names": [
         "\"compact\"",
@@ -751,21 +715,14 @@
     "description": "List of validators, synchronous or asynchronous,\nused by the component\nand the implicit component validators when performing validation. Each item is either an\ninstance that duck types oj.Validator or oj.AsyncValidator.\n<p>\nImplicit validators are created by the element when certain attributes are present.\nFor example, if the <code class=\"prettyprint\">required</code> attribute\nis set, an implicit oj.RequiredValidator is created.\nAt runtime when the component runs validation, it\ncombines all the implicit validators with all the validators\nspecified through this <code class=\"prettyprint\">validators</code> attribute\nand the <code class=\"prettyprint\">async-validators</code> attribute, and\nruns all of them.\n</p>\n<p>\nHints exposed by validators are shown inline by default in the Redwood theme when the\nfield has focus.\nYou can turn off showing validator hints by using the\n'validatorHint' property set to 'none' on the <code class=\"prettyprint\">display-options</code>\nattribute.\n</p>\n<p>\nIn the Redwood theme, only one hint shows at a time, so the precedence rules are:\nhelp.instruction shows; if no help.instruction then validator hints show;\nif none, then help-hints.definition shows; if none, then converter hint shows.\nhelp-hints.source always shows along with the other help or hint.\n</p>\n\n<p>\nWhen <code class=\"prettyprint\">validators</code> property changes due to programmatic\nintervention, the component may decide to clear messages and run validation, based on the\ncurrent state it is in. </br>\n\n<h4>Steps Performed Always</h4>\n<ul>\n<li>The cached list of validator instances are cleared and new validator hints is pushed to\nmessaging.\n</li>\n</ul>\n\n<h4>Running Validation</h4>\n<ul>\n<li>if component is valid when validators changes, component does nothing other than the\nsteps it always performs.</li>\n<li>if component is invalid and is showing messages when\n<code class=\"prettyprint\">validators</code> or\n<code class=\"prettyprint\">async-validators</code> changes then all component messages\n are cleared and full validation run using the display value on the component.\n<ul>\n  <li>if there are validation errors, then <code class=\"prettyprint\">value</code>\n  property is not updated and the error is shown.\n  </li>\n  <li>if no errors result from the validation, the <code class=\"prettyprint\">value</code>\n  property is updated; page author can listen to the <code class=\"prettyprint\">valueChanged</code>\n  event to clear custom errors.</li>\n</ul>\n</li>\n<li>if component is invalid and has deferred messages when validators changes, it does\nnothing other than the steps it performs always.</li>\n</ul>\n</p>\n\n<h4>Clearing Messages</h4>\n<ul>\n<li>Only messages created by the component are cleared.</li>\n<li><code class=\"prettyprint\">messagesCustom</code> property is not cleared.</li>\n</ul>\n</p>",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "defaultvalue": "[]",
     "type": {
       "names": [
         "Array<object>|null"
       ]
-    },
-    "tstype": [
-      {
-        "target": "Type",
-        "value": "Array<AsyncValidator<V>|Validator<V>>|null",
-        "jsdocOverride": true
-      }
-    ]
+    }
   },
   {
     "memberof": "oj-c.TextArea",
@@ -779,7 +736,7 @@
     "description": "The value of the component.\n\n<p>\nWhen <code class=\"prettyprint\">value</code> property changes due to programmatic\nintervention, the component always clears all messages\nincluding <code class=\"prettyprint\">messagesCustom</code>, runs deferred validation, and\nalways refreshes UI display value.\n</p>\n\n<p>\nWhen the textarea field is cleared and the value is committed, the <code class=\"prettyprint\">value</code>\nproperty is set to <code>null</code>.\n</p>\n\n<h4>Running Validation</h4>\n<ul>\n<li>component always runs deferred validation; the\n<code class=\"prettyprint\">valid</code> property is updated with the result.</li>\n</ul>",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "defaultvalue": null,
     "type": {
@@ -808,7 +765,7 @@
     "description": "<p>The  <code class=\"prettyprint\">rawValue</code> is the read-only property for retrieving\nthe current value from the input field in string form. The main consumer of\n<code class=\"prettyprint\">rawValue</code> is a converter.</p>\n<p>\nThe <code class=\"prettyprint\">rawValue</code> updates on the 'input' javascript event,\nso the <code class=\"prettyprint\">rawValue</code> changes as the value of the input is changed.\nIf the user types in '1,200' into the field, the rawValue will be '1', then '1,', then '1,2',\n..., and finally '1,200'. Then when the user blurs or presses\nEnter the <code class=\"prettyprint\">value</code> property gets converted and validated\n(if there is a converter or validators) and then gets updated if valid.\n</p>\n<p>This is a read-only attribute so page authors cannot set or change it directly.</p>",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "type": {
       "names": [
@@ -829,7 +786,7 @@
     "description": "<p>\nThe current valid state of the component. It is evaluated on initial render.\nIt is re-evaluated\n<ul>\n  <li>after each validator (validators or async-validators) is run (full or deferred)</li>\n  <li>when messagesCustom is updated,\n  since messagesCustom can be added by the app developer any time.</li>\n  <li>when showMessages() is called. Since showMessages() moves the\n  hidden messages into messages shown,\n  if the valid state was \"invalidHidden\" then it would become \"invalidShown\".</li>\n  <li>when the required property has changed. If a component is empty and has required\n  set, the valid state may be \"invalidHidden\" (if no invalid messages are being shown as well).\n  If required property is removed, the valid state would change to \"valid\".</li>\n</ul>\n</p>\n<p>\n Note: New valid states may be added to the list of valid values in future releases.\n Any new values will start with \"invalid\"\n if it is an invalid state, \"pending\" if it is pending state,\n and \"valid\" if it is a valid state.\n</p>",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "ojvalues": [
       {
@@ -884,21 +841,22 @@
   },
   {
     "memberof": "oj-c.TextArea",
-    "id": "oj-c.TextArea#reset",
-    "name": "reset",
+    "id": "oj-c.TextArea#blur",
+    "name": "blur",
     "kind": "function",
-    "longname": "oj-c.TextArea#reset",
-    "description": "Resets the component by clearing all messages and messagesCustom attribute\nand updates the component's display value using the attribute value.\nUser entered values will be erased when this method is called.",
+    "longname": "oj-c.TextArea#blur",
+    "description": "Blurs the input field.",
+    "ojhidden": true,
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "scope": "instance",
     "returns": [
       {
         "type": {
           "names": [
-            "any"
+            "void"
           ]
         }
       }
@@ -906,21 +864,22 @@
   },
   {
     "memberof": "oj-c.TextArea",
-    "id": "oj-c.TextArea#showMessages",
-    "name": "showMessages",
+    "id": "oj-c.TextArea#focus",
+    "name": "focus",
     "kind": "function",
-    "longname": "oj-c.TextArea#showMessages",
-    "description": "Takes all deferred messages and shows them.\nIt then updates the valid property;\ne.g., if the valid state was \"invalidHidden\" before showMessages(),\nthe valid state will become \"invalidShown\" after showMessages().\nIf there were no deferred messages this method simply returns.",
+    "longname": "oj-c.TextArea#focus",
+    "description": "Focuses the input field.",
+    "ojhidden": true,
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "scope": "instance",
     "returns": [
       {
         "type": {
           "names": [
-            "any"
+            "void"
           ]
         }
       }
@@ -928,45 +887,43 @@
   },
   {
     "memberof": "oj-c.TextArea",
-    "id": "oj-c.TextArea#validate",
-    "name": "validate",
+    "id": "oj-c.TextArea#showMessages",
+    "name": "showMessages",
     "kind": "function",
-    "longname": "oj-c.TextArea#validate",
-    "description": "If enabled, validates the component's display value using the converter and\nall validators registered on the component and updates the value\noption by performing the following steps.\n<ol>\n<li>All messages are cleared, including custom messages added by the app.</li>\n<li>If the UI display value is empty, then the component normalizes the value to null.</li>\n<li>\n If no converter is present, or the normalized value is null, then processing continues to next step. Otherwise,\n the UI value is first converted (i.e., parsed). If there is a parse error then the messages are shown and processing stops.\n</li>\n<li>\n If required is true, the implicit required validator is run. If the required validator throws an error, the message is shown.\n</li>\n<li>\n If there are no other validators registered on the component, or if the UI display value is empty,\n the value option is updated using the display value (an empty field's display value is null).\n\n Otherwise all validators are run in sequence\n using the parsed value from the previous step.\n When a validation error is encountered it is remembered and the next validator in the sequence is run.\n</li>\n<li>\n At the end of validation if there are errors, the messages are shown.\n If there were no errors, then the value option is updated.\n</li>\n</ol>\n<p>If the component is readonly or disabled, returns a Promise that resolves to 'valid'\nwithout doing any validation.</p>",
+    "longname": "oj-c.TextArea#showMessages",
+    "description": "Takes all deferred messages and shows them.\nIt then updates the valid property;\ne.g., if the valid state was \"invalidHidden\" before showMessages(),\nthe valid state will become \"invalidShown\" after showMessages().\nIf there were no deferred messages this method simply returns.",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "scope": "instance",
     "returns": [
       {
         "type": {
           "names": [
-            "Promise"
+            "void"
           ]
-        },
-        "description": "Promise resolves to \"valid\" if there were no converter parse errors and the component\npassed all validations. The Promise resolves to \"valid\" if the component is disabled or readonly.\nThe Promise resolves to \"invalid\" if there were converter\nparse errors or if there were validation errors."
+        }
       }
     ]
   },
   {
     "memberof": "oj-c.TextArea",
-    "id": "oj-c.TextArea#blur",
-    "name": "blur",
+    "id": "oj-c.TextArea#reset",
+    "name": "reset",
     "kind": "function",
-    "longname": "oj-c.TextArea#blur",
-    "description": "blurs the input field",
-    "ojhidden": true,
+    "longname": "oj-c.TextArea#reset",
+    "description": "Resets the component by clearing all messages and messagesCustom attribute\nand updates the component's display value using the attribute value.\nUser entered values will be erased when this method is called.",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "scope": "instance",
     "returns": [
       {
         "type": {
           "names": [
-            "any"
+            "void"
           ]
         }
       }
@@ -974,24 +931,24 @@
   },
   {
     "memberof": "oj-c.TextArea",
-    "id": "oj-c.TextArea#focus",
-    "name": "focus",
+    "id": "oj-c.TextArea#validate",
+    "name": "validate",
     "kind": "function",
-    "longname": "oj-c.TextArea#focus",
-    "description": "focuses the input field",
-    "ojhidden": true,
+    "longname": "oj-c.TextArea#validate",
+    "description": "If enabled, validates the component's display value using the converter and\nall validators registered on the component and updates the value\noption by performing the following steps.\n<ol>\n<li>All messages are cleared, including custom messages added by the app.</li>\n<li>If the UI display value is empty, then the component normalizes the value to null.</li>\n<li>\n If no converter is present, or the normalized value is null, then processing continues to next step. Otherwise,\n the UI value is first converted (i.e., parsed). If there is a parse error then the messages are shown and processing stops.\n</li>\n<li>\n If required is true, the implicit required validator is run. If the required validator throws an error, the message is shown.\n</li>\n<li>\n If there are no other validators registered on the component, or if the UI display value is empty,\n the value option is updated using the display value (an empty field's display value is null).\n\n Otherwise all validators are run in sequence\n using the parsed value from the previous step.\n When a validation error is encountered it is remembered and the next validator in the sequence is run.\n</li>\n<li>\n At the end of validation if there are errors, the messages are shown.\n If there were no errors, then the value option is updated.\n</li>\n</ol>\n<p>If the component is readonly or disabled, returns a Promise that resolves to 'valid'\nwithout doing any validation.</p>",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "scope": "instance",
     "returns": [
       {
         "type": {
           "names": [
-            "any"
+            "Promise"
           ]
-        }
+        },
+        "description": "Promise resolves to \"valid\" if there were no converter parse errors and the component\npassed all validations. The Promise resolves to \"valid\" if the component is disabled or readonly.\nThe Promise resolves to \"invalid\" if there were converter\nparse errors or if there were validation errors."
       }
     ]
   },
@@ -1004,7 +961,7 @@
     "description": "Sets a property or a single subproperty for complex properties and notifies the component of the change, triggering a corresponding event.",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "scope": "instance",
     "params": [
@@ -1038,7 +995,7 @@
     "description": "Retrieves the value of a property or a subproperty.",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "scope": "instance",
     "params": [
@@ -1067,7 +1024,7 @@
     "description": "Performs a batch set of properties.",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "scope": "instance",
     "params": [
@@ -1096,7 +1053,7 @@
     "memberof": "oj-c.TextArea",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "ojfragment": true
   },
@@ -1109,7 +1066,7 @@
     "memberof": "oj-c.TextArea",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "ojfragment": true
   },
@@ -1125,7 +1082,7 @@
     "description": "Autofocus is a Boolean that reflects the autofocus attribute.\nIf it is set to true then the associated component will get input focus when the page is loaded.\nSetting this property doesn't set the focus to the component:\nit tells the browser to focus to it when the element is inserted in the document.",
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "type": {
       "names": [
@@ -1148,7 +1105,7 @@
     },
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "properties": [
       {
@@ -1204,7 +1161,7 @@
     },
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "properties": [
       {
@@ -1234,7 +1191,7 @@
     },
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "properties": [
       {
@@ -1284,7 +1241,7 @@
     },
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "properties": [
       {
@@ -1308,7 +1265,8 @@
             "\"none\"",
             "\"remaining\""
           ]
-        }
+        },
+        "defaultvalue": "\"remaining\""
       },
       {
         "name": "max",
@@ -1329,7 +1287,7 @@
     "kind": "typedef",
     "longname": "oj-c.TextArea.ComponentMessageItem",
     "scope": "static",
-    "description": "",
+    "description": "A type for a single component message",
     "type": {
       "names": [
         "Object"
@@ -1337,7 +1295,7 @@
     },
     "meta": {
       "filename": "text-area.tsx",
-      "path": "/home/jenkins/uitech/workspace/OJET_Code_16.1.4/packages/oraclejet-core-pack/web/components/oj-c/text-area"
+      "path": "web/components/oj-c/text-area"
     },
     "properties": [
       {