Use ProjectCreated.
The same emitter under the old binding name, so a template still binding (projectCreated) keeps working. Must stay AFTER ProjectCreated: class fields initialise in order, and the other way round this captures undefined.
Use ProjectDeleted.
The same emitter under the old binding name, so a template still binding (projectDeleted) keeps working. Must stay AFTER ProjectDeleted: class fields initialise in order, and the other way round this captures undefined.
Use ProjectSelected.
The same emitter under the old binding name, so a template still binding (projectSelected) keeps working. Must stay AFTER ProjectSelected: class fields initialise in order, and the other way round this captures undefined.
Use ProjectUpdated.
The same emitter under the old binding name, so a template still binding (projectUpdated) keeps working. Must stay AFTER ProjectUpdated: class fields initialise in order, and the other way round this captures undefined.
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ɵfacUse CurrentUser.
Use Disabled.
Use EnvironmentId.
Use ProjectsWithStats.
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 SelectedProject.
Use SelectedProjectId.
Use ShowStats.
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 OnCreateProject.
Use OnDeleteProject.
Use OnEditProject.
Base class for all Angular components in the MemberJunction system.