If specified, this provider will be used for communication and for all metadata purposes. By default, if not provided, the Metadata and RunView classes are used for this and the default GraphQLDataProvider is used which is connected to the same back-end MJAPI instance as the Metadata and RunView classes. If you want to have this component connect to a different MJAPI back-end, create an instance of a ProviderBase sub-class like GraphQLDataProvider/etc, and configure it as appropriate to connect to the MJAPI back-end you want to use, and then pass it in here.
StaticɵdirStaticɵfacDynamic title for the empty state — reflects search vs filter vs truly-empty.
Returns either the default Metadata provider or the one specified in the Provider property, if it was specified
Returns either the default RunQuery provider or the one specified in the Provider property, if it was specified
Returns either the default RunView provider or the one specified in the Provider property, if it was specified
Use ApplyFilters.
Apply filters and sorting
Use ClearSearch.
Clear search
Format date for display
Format expiration for display
Use GetPageNumbers.
Get page numbers to display
Use GetPaginatedKeys.
Get paginated keys
Use GetSortIcon.
Use GetTotalPages.
Get total pages
Go to page
Use LoadKeys.
Load all API keys
A callback method that is invoked immediately after the default change detector has checked data-bound properties if at least one has changed, and before the view and content children are checked.
The changed properties.
A callback method that is invoked immediately after the default change detector has checked the directive's data-bound properties for the first time, and before any of the view or content children have been checked. It is invoked only once when the directive is instantiated.
Use OnSearch.
Handle search input
Use RequestCreate.
Request key creation
Use ToggleSort.
List view component for displaying and filtering API keys