@limetech/lime-elements 37.2.0-next.2 → 37.2.0-next.3

package/dist/types/components/form/form.types.d.ts

@@ -1,4 +1,4 @@
-import { Components } from '@limetech/lime-elements';
+import { Help } from '../help/help.types';
 import { EventEmitter } from '../../stencil-public-runtime';
 export interface ValidationStatus {
   /**
@@ -139,7 +139,7 @@ export interface LimeSchemaOptions {
    * Mark the field as disabled
    */
   disabled?: boolean;
-  help?: string | Components.LimelHelp;
+  help?: string | Help;
 }
 /**
  * Options for a component to be rendered inside a form

package/dist/types/components/help/help.d.ts

@@ -1,5 +1,6 @@
 import { OpenDirection } from '../menu/menu.types';
 import { Link } from '../../interface';
+import { Help as HelpInterface } from './help.types';
 /**
  * A good design is self-explanatory! However, sometimes concepts are
  * too complex to understand, no matter how well-designed a user interface is.
@@ -21,29 +22,21 @@ import { Link } from '../../interface';
  * @exampleComponent limel-example-open-direction
  * @exampleComponent limel-example-placement
  */
-export declare class Help {
+export declare class Help implements HelpInterface {
   /**
-   * The markdown content that will be displayed in the popover.
+   * @inheritdoc
    */
   value: string;
   /**
-   * Visualizes the trigger element. Defaults to: **?**
-   * :::important
-   * Be consistent across the product if you want to change it to a custom character.
-   * All instances of the help component should have the same trigger visualization.
-   * :::
+   * @inheritdoc
    */
   trigger: string;
   /**
-   * If supplied, it will render a "Read more" link at the bottom of the content.
-   * Even though you can add a link anywhere in the content, it is recommended to
-   * use the read more link. Because it will always be displayed at the bottom
-   * of the popover after the content, does not scroll away with the content,
-   * and it will be styled in a consistent way.
+   * @inheritdoc
    */
   readMoreLink?: Link;
   /**
-   * Decides the popover's location in relation to the trigger.
+   * @inheritdoc
    */
   openDirection: OpenDirection;
   private isOpen;

package/dist/types/components/help/help.types.d.ts

@@ -0,0 +1,28 @@
+import { OpenDirection } from '../menu/menu.types';
+import { Link } from '../../interface';
+export interface Help {
+  /**
+   * Decides the popover's location in relation to the trigger.
+   */
+  openDirection: OpenDirection;
+  /**
+   * If supplied, it will render a "Read more" link at the bottom of the content.
+   * Even though you can add a link anywhere in the content, it is recommended to
+   * use the read more link. Because it will always be displayed at the bottom
+   * of the popover after the content, does not scroll away with the content,
+   * and it will be styled in a consistent way.
+   */
+  readMoreLink?: Link;
+  /**
+   * Visualizes the trigger element. Defaults to: **?**
+   * :::important
+   * Be consistent across the product if you want to change it to a custom character.
+   * All instances of the help component should have the same trigger visualization.
+   * :::
+   */
+  trigger: string;
+  /**
+   * The markdown content that will be displayed in the popover.
+   */
+  value: string;
+}

package/dist/types/components.d.ts

@@ -1136,18 +1136,22 @@ export namespace Components {
     interface LimelHelp {
         /**
           * Decides the popover's location in relation to the trigger.
+          * @inheritdoc
          */
         "openDirection": OpenDirection1;
         /**
           * If supplied, it will render a "Read more" link at the bottom of the content. Even though you can add a link anywhere in the content, it is recommended to use the read more link. Because it will always be displayed at the bottom of the popover after the content, does not scroll away with the content, and it will be styled in a consistent way.
+          * @inheritdoc
          */
         "readMoreLink"?: Link;
         /**
           * Visualizes the trigger element. Defaults to: **?** :::important Be consistent across the product if you want to change it to a custom character. All instances of the help component should have the same trigger visualization. :::
+          * @inheritdoc
          */
         "trigger": string;
         /**
           * The markdown content that will be displayed in the popover.
+          * @inheritdoc
          */
         "value": string;
     }
@@ -4961,18 +4965,22 @@ declare namespace LocalJSX {
     interface LimelHelp {
         /**
           * Decides the popover's location in relation to the trigger.
+          * @inheritdoc
          */
         "openDirection"?: OpenDirection1;
         /**
           * If supplied, it will render a "Read more" link at the bottom of the content. Even though you can add a link anywhere in the content, it is recommended to use the read more link. Because it will always be displayed at the bottom of the popover after the content, does not scroll away with the content, and it will be styled in a consistent way.
+          * @inheritdoc
          */
         "readMoreLink"?: Link;
         /**
           * Visualizes the trigger element. Defaults to: **?** :::important Be consistent across the product if you want to change it to a custom character. All instances of the help component should have the same trigger visualization. :::
+          * @inheritdoc
          */
         "trigger"?: string;
         /**
           * The markdown content that will be displayed in the popover.
+          * @inheritdoc
          */
         "value"?: string;
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@limetech/lime-elements",
-  "version": "37.2.0-next.2",
+  "version": "37.2.0-next.3",
   "description": "Lime Elements",
   "author": "Lime Technologies",
   "license": "Apache-2.0",