@bridgeline-digital/hawksearch-handlebars-ui 2.1.0-beta.4 → 3.0.0

package/dist/components/base.component.d.ts

@@ -9,6 +9,10 @@ import { BaseComponentModel } from '@models';
  * @category Base
  */
 export declare abstract class BaseComponent<TConfig extends BaseComponentConfig, TData, TModel extends BaseComponentModel> extends HTMLElement {
+    /**
+     * Optional instance-level configuration to override the global configuration
+     */
+    configOverride?: TConfig;
     /**
      * The data bound to the component.
      */
@@ -60,12 +64,6 @@ export declare abstract class BaseComponent<TConfig extends BaseComponentConfig,
      * The root element which should be used for querying any child elements. This resolves to `this.shadowRoot` if the Shadow DOM is enabled, otherwise `this`.
      */
     get rootElement(): ParentNode;
-    /**
-     * @internal
-     *
-     * @returns Whether the element has a custom template specified through child content.
-     */
-    private get hasContentTemplateOverride();
     /**
      * The name of the event that this component listens to for data binding. if {@link bindFromEvent} is `true`, this prepends `hawksearch:bind-` to {@link componentName} and appends :{@link eventFilter}, if specified.
      *

package/dist/components/index.d.ts

@@ -3,11 +3,10 @@
  *
  * This library was designed to be flexible and allow total customization of the markup used by all components.
  *
- * There are three ways to replace the Handlebars template used by a component:
+ * There are two ways to replace the Handlebars template used by a component:
  *
  * - Pass a template HTML string containing a Handlebars template.
  * - Pass the ID of a template element containing a Handlebars template.
- * - Define the new Handlebars template as the child content of a control
  *
  * *Note: To avoid conflicts with BigCommerce and other systems that Handlebars for server-side rendering, this library also supports an alternate `[[value]]` syntax to work the same as the default Handlerbars `{{value}}` syntax.*
  *
@@ -95,24 +94,6 @@
  *
  * *Note: This approach tends to be easier to manage than the previous option as it is more compatible with popular HTML editors and templates can potentially be loaded from separate files using Server-side Includes (SSI).*
  *
- * ### Setting control content
- *
- * In your HTML file, add the custom markup as the content of a component element:
- *
- * ```html
- * <hawksearch-page-size>
- *   <div class='page-size'>
- *     <select hawksearch-page-size>
- *       {{#each options}}
- *         <option value='{{pageSize}}' {{attribute 'selected' selected}}>{{title}}</option>
- *       {{/each}}
- *     </select>
- *   </div>
- * </hawksearch-page-size>
- * ```
- *
- * *Note: If you choose this approach to customization and need to define a template for a nested element, be aware that by default, Handlebars will try to apply the model from the top-level component to all nested components, which will not work. To guard against this behavior, use the `exclude` helper documented in {@link Helpers.exclude}.*
- *
  * ## Customizing CSS
  * By default, a neutral interface is rendered to get your search instance up and running quickly. However, this library was designed to be customizable and allow developers to use both custom markup and custom CSS.
  *