Skip to content

Events and Handlers

The Autocomplete Google Places component has the following events and handlers available for use:

Events

Event
Description
On Before Mount
Triggers immediately before the component is mounted and appeared on the page.
On Mounted
Triggers immediately after the component is mounted and appeared on the page.
On Before Unmount
Triggers immediately before the component is unmounted and destroyed. Perform any necessary cleanup in this method, such as invalidating timers or cleaning up any RT subscriptions that were created in this component.
On Change Event
Triggers the event when the component's state (value) changes.
On Focus Event
Fires the event when the component receives the focus for data entry or by pressing the TAB key.
On Lost Focus Event
Triggers when the component loses focus.
On Visibility Change
Gets activated when the visibility state of the component is altered. You can use this event to define actions that need to take place when the component becomes visible or hidden.
On Key Down Event
Triggers when the key was pressed.

Handlers

Handler
Description
Class List Logic
This logic involves modifying the CSS classes associated with the component dynamically.
Styles Logic
Allows you to change the styles of the component dynamically.
Visibility Logic
Allows controlling the visibility of the component based on certain conditions. You can use this event to show or hide the component depending on user actions or other factors. If the handler returns true, the component will be visible.
Label Logic
Determines the value of the component's label. The value returned by the event handler will be used as the component label.
Value Logic
Contains logic to determine the value of the component. The autocomplete value is what the user enters or using this handler your logic can determine it.
Autocomplete Predictions
Contains logic to determine the autocomplete predictions settings for the component.
Search Box Predictions
Contains logic to determine the search box predictions settings for the component.
Placeholder Logic
Contains logic to define a component placeholder. An autocomplete placeholder is what the user sees before filling in the autocomplete or using this handler your logic can determine this.
Read-Only State Logic
Contains logic to determine if the autocomplete component should be read-only. When the handler returns true, the autocomplete component becomes read-only.
Disabled State Logic
Determines if the component should be disabled. If the handler returns true, the component will be disabled.
Required State Logic
Using this handler you can dynamically configure the component as required. A required component prevents form submission until it has a value.