async
component enables us to rerender/defer parts of the UI based on events/timing without full page reload.async
core component does get loaded and displayed on initial pageload!async
core component accepts the following parameters:async
component needs an ID in order to resolve the correct content on an async HTTP requestrerender_on
option lets us define an event on which the component gets rerendered.rerender_on
option lets you rerender parts of your UI asynchronously. But please consider that, if not configured differently, itdefer
option may be used in two ways:defer: true
implies that the content of the async
component gets requested within a separate GET request right after initial page load is done.defer: 2000
means that the content of the async
component gets requested within a separate GET request 2000 milliseconds after initial page load is done.async
component with activated defer
behavior is not resolved within the first page load!SomeModel.some_query
does not get executed within the first page load and only will be called within the deferred GET request. This helps us to render a complex UI with loads of heavy method calls step by step without slowing down the initial page load and rendering of simple content.loading
class will automatically be applied, which can be used for CSS styling and animations:async
component to request its content directly after the page load or to delay the request for a given amount of time after the page load. :defer
expects either a boolean or a integer representing the delay time in milliseconds. If :defer
is set to false
the async
component will be rendered on page load and not deferred. If set to true
it will request its content directly after the page load.async
component will be rendered asynchronously after page load.defer: 500
will delay the asynchronous request after page load of the async
component for 300ms and render the content afterwards.async
leverages the event hub and can react to emitted events. If it receives one or more of the with :rerender_on
specified events it will asynchronously request a rerender of its content. The response will only include the rerendered html of the async
component which then replaces the current content of the async
. If you specify multiple events in :rerender_on
they need to be seperated by a comma.async
component wrapping the paragraph receives the event and reacts to it by requesting its rerendered content from the server and replacing its content with the received html. In this case it will rerender after button click and show the updated time.