Property decorator for letting a component automatically query an element with specified characteristics. The result is kept in sync with the page model as element updates arrive.

Property decorator for letting a component automatically query for elements with specified characteristics. The result is kept in sync with the page model as element updates arrive.

Decorator function to go along the Angular ComponentDecorator to specify the details of a Blueriq component.

Creates a component matcher from a CSS-like selector. Optionally allows for specifying a priority offset when the priority as computed from the selector is desired to be changed.

For scoped components that are registered with BlueriqComponents.scoped, it is advised to use this function as it ensures the selector is only compiled once. Furthermore, any errors that may occur from the compilation of the selector become apparent during startup, instead of during the first time the component is in scope.

Any errors that occur during the compilation of the selector will not be handled gracefully as would be the case when a raw string selector would have been used.

Given a Blueriq element, returns the Angular ComponentRef that was rendered for the element. This may be undefined, in the case where the element has not been rendered using BqElementDirective.

Returns a set of field messages as currently registered on the form control. This is different from using Blueriq's Field.messages in the sense that a form control's messages may include frontend validation results as the user is currently typing in the form control.

Determines if the error is recognized as BlueriqResponseError, optionally requiring a specific type of error. If an error is not recognized as such, it may be because of several reasons such as the following:

1. No internet connection or network related glitches
2. Incorrect backend/proxy configuration, resulting in endpoints not being found.

Augments the original URL with a query parameter that causes the Runtime to redirect to the provided error redirect URL if processing of the request fails.

This is relevant when file downloads are performed using a GET request by changing the browser's URL. Normally, such requests would result in a "Content-Disposition: attachment" response, which will cause the browser to download the response's content and abort the GET redirect. In failure situations however, no "Content-Disposition" response can be sent so the browser will follow the GET redirect, which results in showing a page with some JSON data. This can be prevented by sending along an "error redirect" URL that will cause a "302 Found" response with the provided URL to be generated instead, such that the browser follows the redirect to the desired location.

If you are consuming downloads using XHR, then you do actually want to receive JSON responses instead of following a redirect. In that case, simply do not use this function and handle the JSON error response instead.

Note: this only has effect when using the V2 API, as V1 does not support arbitrary redirect upon failures but instead always redirects to its internal error static page.

An URL that mirrors the original URL with an error redirect query parameter added.