class MeetingInfo
An abstract base class that serves as a container for meeting-specific information, inheriting from ClientValue to provide serialization capabilities for Office 365 API interactions.
/tf/active/vicechatdev/SPFCsync/venv/lib64/python3.11/site-packages/office365/communications/meetings/info.py
4 - 5
simple
Purpose
MeetingInfo is an abstract class designed to be subclassed for representing various types of meeting-related data in Office 365 integrations. It inherits from ClientValue, which provides JSON serialization/deserialization capabilities for client-server communication. This class serves as a foundation for concrete meeting information classes that will contain specific meeting details such as participants, schedules, locations, or other meeting metadata. It is not meant to be instantiated directly but rather extended by concrete implementations.
Source Code
class MeetingInfo(ClientValue):
"""An abstract class that contains meeting-specific information."""
Parameters
| Name | Type | Default | Kind |
|---|---|---|---|
bases |
ClientValue | - |
Parameter Details
bases: Inherits from ClientValue, which provides the base functionality for client-side value objects that can be serialized to and from JSON for Office 365 API communication
Return Value
When subclassed and instantiated, returns an instance of the concrete meeting information class that can be serialized for Office 365 API requests and deserialized from API responses. The base MeetingInfo class itself should not be instantiated as it is abstract.
Class Interface
Dependencies
office365
Required Imports
from office365.runtime.client_value import ClientValue
Usage Example
# MeetingInfo is abstract and should be subclassed
# Example of creating a concrete implementation:
from office365.runtime.client_value import ClientValue
class ConcreteMeetingInfo(MeetingInfo):
def __init__(self, subject=None, start_time=None, end_time=None):
super().__init__()
self.subject = subject
self.start_time = start_time
self.end_time = end_time
# Usage:
meeting = ConcreteMeetingInfo(
subject="Team Standup",
start_time="2024-01-15T10:00:00",
end_time="2024-01-15T10:30:00"
)
# The object can now be serialized for API calls
# meeting_data = meeting.to_json()
Best Practices
- Do not instantiate MeetingInfo directly; always create concrete subclasses that implement specific meeting information structures
- Ensure subclasses define appropriate attributes for the specific meeting information they represent
- Leverage the ClientValue parent class methods for JSON serialization when communicating with Office 365 APIs
- Follow Office 365 API schema requirements when defining attributes in concrete implementations
- Use type hints in concrete implementations to improve code clarity and IDE support
- Consider implementing __init__ methods in subclasses to initialize meeting-specific attributes
- Maintain immutability where possible to prevent unintended state changes during API operations
Tags
Similar Components
AI-powered semantic similarity - components with related functionality:
-
class MeetingParticipantInfo 73.3% similar
-
class MeetingParticipants 68.5% similar
-
class AttachmentInfo 67.0% similar
-
class JoinMeetingIdMeetingInfo 66.9% similar
-
class WebInfoCreationInformation 63.0% similar