All entity fields for looking up field information
Use ClosePanel.
The same emitter under the old binding name, so a template still binding (closePanel) keeps working. Must stay AFTER ClosePanel: class fields initialise in order, and the other way round this captures undefined.
Emitted when user clicks the close button
Use EntitySelected.
The same emitter under the old binding name, so a template still binding (entitySelected) keeps working. Must stay AFTER EntitySelected: class fields initialise in order, and the other way round this captures undefined.
Emitted when a related entity is selected (clicked in relationships list)
Whether the fields section is expanded
Use FieldsSectionToggle.
The same emitter under the old binding name, so a template still binding (fieldsSectionToggle) keeps working. Must stay AFTER FieldsSectionToggle: class fields initialise in order, and the other way round this captures undefined.
Emitted when fields section is toggled
Use OpenEntity.
The same emitter under the old binding name, so a template still binding (openEntity) keeps working. Must stay AFTER OpenEntity: class fields initialise in order, and the other way round this captures undefined.
Emitted when user clicks to open the entity record
Use OpenRecord.
The same emitter under the old binding name, so a template still binding (openRecord) keeps working. Must stay AFTER OpenRecord: class fields initialise in order, and the other way round this captures undefined.
Emitted when requesting to open an entity record
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.
Whether the relationships section is expanded
Use RelationshipsSectionToggle.
The same emitter under the old binding name, so a template still binding (relationshipsSectionToggle) keeps working. Must stay AFTER RelationshipsSectionToggle: class fields initialise in order, and the other way round this captures undefined.
Emitted when relationships section is toggled
The currently selected entity to display details for
StaticɵdirStaticɵfacUse AllEntityFields.
Use ExpandedFieldDetails.
Use ExpandedFieldValues.
Use FieldFilter.
Use FieldsListContainer.
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 SelectedEntity.
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.
Use OnClosePanel.
Use OnOpenEntity.
Use SetFieldFilter.
Use ToggleFieldsSection.
Entity details panel component that displays detailed information about a selected entity. Shows entity metadata, fields with filtering capabilities, and related entities.
This component is designed to be used alongside the ERD diagram to provide a detailed view of the currently selected entity.