Skip to content

A compact tool to provide an autocomplete option to a user's input. Similar to JQuery UI `.autocomplete()`

License

Notifications You must be signed in to change notification settings

TopMarksDevelopment/JavaScript.Autocomplete

Repository files navigation

Autocomplete (A JavaScript package)

GitHub Actions Workflow Status

A small package to provide an autocomplete list as a user is typing.

Contents

Features

  • Supports different sources; whether string, object, array or callback
  • Allows specification of the source type with strong types
  • Complete control over construction, with custom renderers
  • Option to automatically focus on the first element when the menu opens
  • Configurable delay between keystrokes and source calls
  • Supports a minimum term, before querying the source
  • Custom mapping of object properties to the generic type
  • Flexible positioning of the autocomplete box
  • Ability to append the menu to a specific element
  • Event callbacks for menu interactions and lifecycle events

Usage

Basic usage

ℹ️ Without specifying a type, autocomplete defaults to the generic type:
{ label: string; value: string }

// Using the default options (source is always required)
new Autocomplete(
    '.autocomplete',
    {
        // Query this source & expect a JSON response
        source: './relative-folder/query.html'
        // or './relative-folder/{{term}}/query'
    }
)
    // Don't forget to start it
    .start();

Strong Types

As the package is written in TypeScript, you can specify the source's type.

With the type specified you can write your TypeScript with strong type definitions!

In this example I've provided an array of inputs (that will always be returned) - this is also strongly typed!

type MyType = {
    myCustomName: string;
    myCustomValue: string;
}

// Specifying MyType means "source" is now tightly-bound
new Autocomplete<MyType>(
    '.autocomplete',
    {
        source: [
            {
                myCustomName: "One - Name",
                myCustomValue: "One - Value"
            },
            {
                myCustomName: "Two - Name",
                myCustomValue: "Two - Value"
            },
            {
                myCustomName: "Three - Name",
                myCustomValue: "Three - Value"
            },
        ]
    },
    renderers: {
        itemRenderer: ({ item }) =&gt; {
            const li = document.createElement('li');

            li.dataset.value = item.myCustomName;

            // li.innerText = item.detail;
            //  The above would now throw:
            //  "Property 'detail' does not exist on type 'MyType'"

            li.innerText = item.myCustomValue;

            return li;
        },
    }
)
    // Don't forget to start it
    .start();

Options

source: SourceTypes<T>

The source of the autocompelte data

SourceTypes<T>

  • string
    a URL that we will GET, expecting a JSON response.
    Note: the search term is added to the URL in one of two ways
    • if {{term}} is in the URL, this will be replaced, else
    • a term querystring parameter is appended to the URL
  • Record set
    an object with string keys and values, treated as label, value respectively
  • string[]
    an array of strings with each item treated as both the value and label
  • T[]
    an array of the generic type (if specified)
  • function(string) => _ONE OF THE ABOVE
    a function that receives { term } and returns one of the above sets

autoFocus?: boolean

Automatically focus on the first element when the menu opens
Default: false

delay?: number

The delay (in milliseconds) between a keystroke and a search. This acts like a throttle between source calls
Default: 300

minLength?: number

Minimum term entered by the user before we query the source
Default: 2

recordMapper?: (input: Record<string, string>) => T[]

Define how an object should be mapped to the type T
Default: An array where the property name becomes label and it's value becomes value

position?: IPositionData

How shold the autocomplete box positioned
Default: { my: "top center", at: "botom center" }

renderers?: IRenderers;

Specify how we render the elements

appendTo?: HTMLElement

Append the menu to this element, instead of the body

logger?: JavascriptLogger

Log stages of the autocomplete processes

Option Methods

onClose

Called after the menu has been closed
Call:

onClose: (ev: Event, data: { ul: HTMLUListElement }) => {}

onCreated

Called after the menu has been created, but before being opened
Call:

onCreated: (ev: Event, data: { ul: HTMLUListElement }) => {}

onItemFocus

Called as soon as an item is focused, but before changing its state
Call:

// T is your generic type, if specified
onItemFocus: (
    ev: Event,
    data: {
        ul: HTMLUListElement
        item: <T>,
        input: HTMLInputElement
    }
) => {}

onItemSelect

Called as soon as an item is selecetd, but before changing any state
Call:

// T is your generic type, if specified
onItemSelect: (
    ev: Event,
    data: {
        ul: HTMLUListElement
        item: <T>,
        input: HTMLInputElement
    }
) => {}

onOpen

Called before the menu has been opened and any position data is calculated
Call:

onOpen: (ev: Event, data: { ul: HTMLUListElement }) => {}

onResponse

Called after processing the response and before creating the menu
Call:

// T is your generic type, if specified
onResponse: (ev: Event, data: { items: T[] }) => {}

onSearch

Called before processing the search
Call:

onSearch: (ev: Event, data: { term: string }) => {}

onStart

A method called after events have been added
Call:

onStart: () => {}

onStop

A method called after events have been removed
Call:

onStop: () => {}