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ɵfacReturns 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 RunReport 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
Cancels changes and reverts to saved state
Clears the icon search
Clears uploaded file
Extracts the icon name from a Font Awesome class string e.g., "fa-solid fa-user-tie" -> "user-tie"
Checks if an icon is currently selected
A callback method that performs custom clean-up, invoked immediately before a directive, pipe, or service instance is destroyed.
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.
Handles file selection from native input
Handles icon search input changes
Handles URL input changes
Reverts avatar to default (clears both fields) This will trigger auto-sync from auth provider on next login
Saves avatar settings to database
Handles icon selection
Switches between tabs and updates preview
Syncs avatar from authentication provider NOTE: This is a placeholder - actual implementation should be done in the calling application which has access to auth services
Base class for all Angular components in the MemberJunction system.