Typeahead control for Blazor applications.
You can install from NuGet using the following command:
Install-Package Blazored.Typeahead
Or via the Visual Studio package manger.
Blazor Server applications will need to include the following CSS and JS files in their _Host.cshtml
.
In the head
tag add the following CSS.
<link href="_content/Blazored.Typeahead/blazored-typeahead.css" rel="stylesheet" />
Then add the JS script at the bottom of the page using the following script tag.
<script src="_content/Blazored.Typeahead/blazored-typeahead.js"></script>
NOTE If you're using Blazor WebAssembly then these files will get added to your index.html
automagically.
I would also suggest adding the following using statement to your main _Imports.razor
to make referencing the component a bit easier.
@using Blazored.Typeahead
The component can be used standalone or as part of a form. When used in a form the control fully integrates with Blazors forms and authentication system.
Below is a list of all the options available on the Typeahead.
Templates
ResultTemplate
(Required) - Allows the user to define a template for a result in the results listSelectedTemplate
(Required) - Allows the user to define a template for a selected itemNotFoundTemplate
- Allows the user to define a template when no items are foundFooterTemplate
- Allows the user to define a template which is displayed at the end of the results list
Parameters
MinimumLength
(Optional - Default: 1) - Minimum number of characters before starting a searchDebounce
(Optional - Default: 300) - Time to wait after last keypress before starting a searchMaximumSuggestions
(Optional - Default: 10) - Controls the amount of suggestions which are shownDisabled
(Optional - Default: false) - Marks the control as disabled and stops any interactionEnableDropDown
(Optional - Default: false) - Allows the control to behave as a dropdownShowDropDownOnFocus
(Optional - Default: false) - When enabled, will show the suggestions dropdown automatically when the control is in search mode. If the control has a current value then the user would need to press the enter key first to enter search mode.
The control also requires a SearchMethod
to be provided with the following signature Task<IEnumerable<TItem>>(string searchText)
. The control will invoke this method
passing the text the user has typed into the control. You can then query your data source and return the result as an IEnumerable
for the control to render.
If you wish to bind the result of the selection in the control to a different type than the type used in the search this is also possible. For example, if you passed in a list
of Person
but when a Person
was selected you wanted the control to bind to an int
value which might be the Id
of the selected Person
, you can achieve this by providing
a ConvertMethod
The convert method will be invoked by the control when a selection is made and will be passed the type selected. The method will need to handle the conversion
and return the new type.
<EditForm Model="MyFormModel" OnValidSubmit="HandlValidSubmit">
<BlazoredTypeahead SearchMethod="SearchFilms"
@bind-Value="MyFormModel.SelectedFilm">
<SelectedTemplate>
@context.Title
</SelectedTemplate>
<ResultTemplate>
@context.Title (@context.Year)
</ResultTemplate>
</BlazoredTypeahead>
<ValidationMessage For="@(() => MyFormModel.SelectedFilm)" />
</EditForm>
@code {
[Parameter] protected IEnumerable<Film> Films { get; set; }
private async Task<IEnumerable<Film>> SearchFilms(string searchText)
{
return await Task.FromResult(Films.Where(x => x.Title.ToLower().Contains(searchText.ToLower())).ToList());
}
}
In the example above, the component is setup with the minimum requirements. You must provide a method which has the following signature Task<IEnumerable<T> MethodName(string searchText)
, to the SearchMethod
parameter. The control will call this method with the current search text everytime the debounce timer expires (default: 300ms). You must also set a value for the Value
parameter. This will be populated with the item selected from the search results. As this version of the control is integrated with Blazors built-in forms and validation, it must be wrapped in a EditForm
component.
The component requires two templates to be provided...
SelectedTemplate
ResultTemplates
The SelectedTemplate
is used to display the selected item and the ResultTemplate
is used to display each result in the search list.
@inject HttpClient httpClient
<BlazoredTypeahead SearchMethod="@SearchFilms"
@bind-Value="@SelectedFilm"
Debounce="500">
<SelectedTemplate>
@context.Title
</SelectedTemplate>
<ResultTemplate>
@context.Title (@context.Year)
</ResultTemplate>
<NotFoundTemplate>
Sorry, there weren't any search results.
</NotFoundTemplate>
</BlazoredTypeahead>
@code {
[Parameter] protected IEnumerable<Film> Films { get; set; }
private async Task<IEnumerable<Film>> SearchFilms(string searchText)
{
var response = await httpClient.GetJsonAsync<IEnumerable<Film>>($"https://allfilms.com/api/films/?title={searchText}");
return response;
}
}
Because you provide the search method to the component, making a remote call is really straight-forward. In this example, the Debounce
parameter has been upped to 500ms and the NotFoundTemplate
has been specified.