Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\AdminCreateCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\AppointmentUpdateEquipmentCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\CheckUnpaidInvoiceCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\ClinicDeleteAppointmentsCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\ClinicRemovePatientsCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\ClinicTopicsCreateCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\CreateClinicVoucherCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\CreateDefaultPatientStatusesCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\CreateSessionTableCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\CreateStripePaymentTypeCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\DeleteClinicAnswersCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\DestroySessionCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\DownloadFileCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\ExportClinic" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\GoogleCalendarCheckCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\GoogleEventAddCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\GoogleEventAddRoomCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\GoogleEventAddTreatmentCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\GoogleEventCheckCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\ICalendarExportCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\ImportFilesByClinicCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\ImportMongoCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\ImportMySqlCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\LearnAboutSourcesCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\MailchimpPatientsUpdateCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\OnlineBookingAddHashToWidgetCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\OnlineBookingNotConfirmedAppointmentCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\Paymentsense\CreatePaymentsensePaymentTypesCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\Paymentsense\EndOfDayReports" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\PdfCreateCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\ProcessCampaignTrackingCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\ProcessCorrespondenceTrackingCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\ProcessFilterCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\ProcessFilterTestCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\RemoveOldArchive" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\ReplaceOldPrepayCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\SendSmsCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\SetPatientsCreatedByCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\SmsCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\Temporary\MigrateLearnAbout" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\Temporary\PriceTier\CreatePriceTiersCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\Temporary\PriceTier\MigrateToNewPriceTierStructureCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\Temporary\PriceTier\MigrateToPriceTiersCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\TermsAndCondCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\TestFixturesLoaderCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\ThumborCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\UpdateClinicSharing" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\UpdateClinicSharingNew" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\UpdateNewClinicAutomatic" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\UpdatePhotoNotesCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Console\Command\Command::configure()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Command\XeroDataSynchronizeCommand" now to avoid errors or add an explicit @return annotation to suppress this message.
App\Controller\Admin\Clinic\DefaultController::zoomMeetingPage(): Optional parameter $meetingId declared before required parameter $paginator is implicitly treated as a required parameter
App\Controller\Admin\LeadCapturePipelineController::saveEmailAndMessage(): Optional parameter $subject declared before required parameter $type is implicitly treated as a required parameter
App\Controller\Api\Clinic\DefaultController::treatmentsList(): Implicitly marking parameter $text as nullable is deprecated, the explicit nullable type must be used instead
App\Controller\Api\DefaultController::returnEmailTemplateForOTP(): Optional parameter $username declared before required parameter $otp is implicitly treated as a required parameter
App\Controller\CustomFormDataController::customformdata_index(): Optional parameter $formid declared before required parameter $paginator is implicitly treated as a required parameter
App\Controller\CustomFormDataController::eventformdata_index(): Optional parameter $formid declared before required parameter $paginator is implicitly treated as a required parameter
App\Controller\DefaultController::returnEmailTemplateForOTP(): Optional parameter $username declared before required parameter $otp is implicitly treated as a required parameter
App\Controller\EventController::appointmentlead_details(): Implicitly marking parameter $appointmentlead as nullable is deprecated, the explicit nullable type must be used instead
App\Controller\EventController::appointmentleadJoin(): Implicitly marking parameter $appointmentlead as nullable is deprecated, the explicit nullable type must be used instead
App\Controller\OpenController::silentPost(): Implicitly marking parameter $post as nullable is deprecated, the explicit nullable type must be used instead
App\Controller\TemplateController::library(): Optional parameter $category_id declared before required parameter $qtype is implicitly treated as a required parameter
App\Controller\TemplateController::clinic_templates(): Optional parameter $category_id declared before required parameter $qtype is implicitly treated as a required parameter
App\Controller\YourController::silentPost(): Implicitly marking parameter $post as nullable is deprecated, the explicit nullable type must be used instead
App\DataFixtures\Faker\Loader::load(): Implicitly marking parameter $purgeMode as nullable is deprecated, the explicit nullable type must be used instead
Method "Doctrine\Common\EventSubscriber::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "App\EventListener\AppointmentSubscriber" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\Common\EventSubscriber::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "App\EventListener\ClinicDoctrineSubscriber" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "App\EventListener\ClinicSubscriber" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\Common\EventSubscriber::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "App\EventListener\ClinicUserSubscriber" now to avoid errors or add an explicit @return annotation to suppress this message.
App\EventListener\DoctrineExtensionSubscriber::__construct(): Optional parameter $blameableListener declared before required parameter $tokenStorage is implicitly treated as a required parameter
Method "Symfony\Component\EventDispatcher\EventSubscriberInterface::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "App\EventListener\DoctrineExtensionSubscriber" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\Common\EventSubscriber::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "App\EventListener\FormFileSubscriber" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\Common\EventSubscriber::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "App\EventListener\InvoiceSubscriber" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\Common\EventSubscriber::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "App\EventListener\MediaSubscriber" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\Common\EventSubscriber::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "App\EventListener\PatientDocumentSubscriber" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Doctrine\Common\EventSubscriber::getSubscribedEvents()" might add "array" as a native return type declaration in the future. Do the same in implementation "App\EventListener\PatientFormSubscriber" now to avoid errors or add an explicit @return annotation to suppress this message.
App\EventListener\RateLimitSubscriber::__construct(): Implicitly marking parameter $tokenStorage as nullable is deprecated, the explicit nullable type must be used instead
App\ExportImport\CampaignDataExport::setUser(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead
App\ExportImport\CampaignDataExport::setClinic(): Implicitly marking parameter $clinic as nullable is deprecated, the explicit nullable type must be used instead
App\ExportImport\CriteriaExport::setUser(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead
App\ExportImport\CriteriaExport::setClinic(): Implicitly marking parameter $clinic as nullable is deprecated, the explicit nullable type must be used instead
App\ExportImport\ExportAllData::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\ExportImport\ExportDetailInterface::countAllRecordsDetail(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\ExportImport\ExportInterface::countAllRecords(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\ExportImport\ServiceCSV::exportQuestionnaires(): Implicitly marking parameter $questionaire as nullable is deprecated, the explicit nullable type must be used instead
App\ExportImport\ServiceCSV::exportAllPhotoData(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\ExportImport\ServiceCSV::exportAllData(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\ExportImport\ServiceCSV::createFileTitle(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\CampaigndetailsType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\CampaigndetailsType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\CustomReports\CustomReportsFilterForm" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\CustomReports\CustomReportsFilterForm" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\CustomReports\CustomReportsForm" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\CustomReports\CustomReportsForm" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\CustomReports\FavoriteCustomReportsForm" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\CustomReports\FavoriteCustomReportsForm" now to avoid errors or add an explicit @return annotation to suppress this message.
App\Form\Model\CustomFilter::setClinic(): Implicitly marking parameter $clinic as nullable is deprecated, the explicit nullable type must be used instead
App\Form\Model\DashboardFilter::setClinic(): Implicitly marking parameter $clinic as nullable is deprecated, the explicit nullable type must be used instead
App\Form\Model\DashboardFilter::addClinic(): Implicitly marking parameter $clinic as nullable is deprecated, the explicit nullable type must be used instead
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Model\MailChimpWebhookDataMergeFieldsType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Model\MailChimpWebhookDataMergeFieldsType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Model\MailChimpWebhookDataMergeFieldsType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Model\MailChimpWebhookDataType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Model\MailChimpWebhookDataType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Model\MailChimpWebhookDataType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Model\MailChimpWebhookRequestType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Model\MailChimpWebhookRequestType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Model\MailChimpWebhookRequestType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\ParseApiFilterForm" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\ParseApiFilterForm" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\ParseApiFilterForm" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\AddPasswordType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\AddPasswordType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\AddPasswordType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Appointment\AppointmentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Appointment\AppointmentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Appointment\AppointmentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Appointment\GoogleEventDaySheetStatusType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Appointment\GoogleEventDaySheetStatusType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Appointment\GoogleEventDaySheetStatusType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Appointment\GoogleEventType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Appointment\GoogleEventType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Appointment\GoogleEventType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Appointment\SearchFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Appointment\SearchFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Appointment\SearchFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\AppointmentCodeType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\AppointmentCodeType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\AppointmentCodeType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\BlockerReasonType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\BlockerReasonType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\BlockerReasonType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Campaign\CampaignType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Campaign\CampaignType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Campaign\CampaignType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Chronoscan\SettingsType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Chronoscan\SettingsType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Chronoscan\SettingsType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ClinicBrandingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ClinicBrandingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ClinicBrandingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ClinicEventsReminderType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ClinicEventsReminderType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ClinicEventsReminderType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ClinicMeetingsReminderType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ClinicMeetingsReminderType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ClinicMeetingsReminderType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ClinicReminderRecallType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ClinicReminderRecallType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ClinicReminderRecallType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ClinicReminderType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ClinicReminderType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ClinicReminderType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ClinicType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ClinicType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ClinicType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\DeclarationType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\DeclarationType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\DiscountReasonType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\DiscountReasonType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\DiscountReasonType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\DocumentCategoryType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\DocumentCategoryType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\DocumentCategoryType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\EmailTemplate\EmailTemplateType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\EmailTemplate\EmailTemplateType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\EmailTemplate\EmailTemplateType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\EquipmentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\EquipmentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\EquipmentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Filter\InvoiceType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Filter\InvoiceType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Filter\ProfileType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Filter\ProfileType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Filter\TreatmentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Filter\TreatmentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Filter\TreatmentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\FormFileType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\FormFileType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\FormFileType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\LearnAboutSourceType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\LearnAboutSourceType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\LearnAboutType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\LearnAboutType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\LocationType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\LocationType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\LocationType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\MailChimpType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\MailChimpType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\MailChimpType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\MarketingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\MarketingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\MarketingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\MeetingReminderType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\MeetingReminderType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\MeetingReminderType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Membership\MembershipItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Membership\MembershipItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Membership\MembershipItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Membership\MembershipType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Membership\MembershipType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Membership\MembershipType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\NotConvertReasonType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\NotConvertReasonType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\NotConvertReasonType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\OnlineBooking\EmailSettingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\OnlineBooking\EmailSettingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\OnlineBooking\EmailSettingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\OnlineBooking\SettingsType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\OnlineBooking\SettingsType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\OnlineBooking\SettingsType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\OnlineBooking\WidgetType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\OnlineBooking\WidgetType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\OnlineBooking\WidgetType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\OutcomeType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\OutcomeType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\OutcomeType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\PatientStatus\PatientStatusType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\PatientStatus\PatientStatusType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\PatientStatus\PatientStatusType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Person\ClinicUserType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Person\ClinicUserType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Person\ClinicUserType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Person\DailyScheduleType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Person\DailyScheduleType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Person\DailyScheduleType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\PolicyEditType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\PolicyEditType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\PolicyEditType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\PolicyType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\PolicyType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\PolicyType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\PostAptFormType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\PostAptFormType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\PostAptFormType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\PriceTier\PriceTierType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\PriceTier\PriceTierType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\PriceTier\PriceTierType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Questionaire\AnswerType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Questionaire\AnswerType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Questionaire\AnswerType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Questionaire\QuestionAnswerType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Questionaire\QuestionAnswerType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Questionaire\QuestionAnswerType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Questionaire\QuestionType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Questionaire\QuestionType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Questionaire\QuestionType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Questionaire\QuestionaireExportFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Questionaire\QuestionaireExportFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Questionaire\QuestionaireExportFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Questionaire\QuestionaireQuestionType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Questionaire\QuestionaireQuestionType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Questionaire\QuestionaireQuestionType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Questionaire\QuestionaireType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Questionaire\QuestionaireType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Questionaire\QuestionaireType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Register\FormFilesType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Register\FormFilesType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Register\PaymentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Register\PaymentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Register\PaymentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Register\ProductsType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Register\ProductsType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Register\ProductsType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Register\ProfileType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Register\ProfileType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Register\ProfileType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Register\TreatmentsType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Register\TreatmentsType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Register\TreatmentsType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ReminderRecallType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ReminderRecallType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ReminderRecallType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ReminderType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ReminderType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\ReminderType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\RoomType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\RoomType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\RoomType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\SearchFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\SearchFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\SearchFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\SpecialOfferType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\SpecialOfferType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\SpecialOfferType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\AdjustStockType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\AdjustStockType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\AdjustStockType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\GoodsReceivedType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\GoodsReceivedType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\GoodsReceivedType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\ItemGoodsReceivedType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\ItemGoodsReceivedType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\ItemGoodsReceivedType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\PractitionerPricingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\PractitionerPricingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\PractitionerPricingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\PrepayPackageItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\PrepayPackageItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\PrepayPackageItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\PrepayPackageType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\PrepayPackageType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\PrepayPackageType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\PriceListType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\PriceListType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\PriceListType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\ProductType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\ProductType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\ProductType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\SopsPolicyTemplateType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\SopsPolicyTemplateType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\SopsPolicyTemplateType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\Treatment\AddEquipmentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\Treatment\AddEquipmentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\Treatment\AddEquipmentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\Treatment\AddProductType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\Treatment\AddProductType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\Treatment\AddProductType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\Treatment\AddTreatmentCategoryType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\Treatment\AddTreatmentCategoryType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\Treatment\AddTreatmentCategoryType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\Treatment\AddTreatmentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\Treatment\AddTreatmentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\Treatment\AddTreatmentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\Treatment\CheckListItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\Treatment\CheckListItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\Treatment\CheckListItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\TreatmentCategoryGroup" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\TreatmentCategoryGroup" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\TreatmentCategoryGroup" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\TreatmentClinicType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\TreatmentClinicType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\TreatmentClinicType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\TreatmentGroupType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\TreatmentGroupType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\TreatmentGroupType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\TreatmentNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\TreatmentNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\Stock\TreatmentNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\SurveyType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\SurveyType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\SurveyType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\TaskBoardType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\TaskBoardType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\TaskBoardType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\TaskItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\TaskItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\TaskItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\TermsAndCondType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\TermsAndCondType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\TreatmentPlanTermsAndCondType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\TreatmentPlanTermsAndCondType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\TwilioType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\TwilioType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Clinic\TwilioType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Dashboard\DashboardFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Dashboard\DashboardFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Dashboard\DashboardFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\DaySheet\DaySheetType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\DaySheet\DaySheetType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\DaySheet\DaySheetType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\DaySheet\SearchFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\DaySheet\SearchFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\EventType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\EventType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\HealthXChange\LoginType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\HealthXChange\LoginType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\HealthXChange\LoginType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\HealthXChange\SearchType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\HealthXChange\SearchType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\HealthXChange\SearchType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Help\HelpType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Help\HelpType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Help\HelpType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Invoice\InvoiceFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Invoice\InvoiceFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Invoice\InvoiceFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\LeadCapture\LeadCapturePipelineType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\LeadCapture\LeadCapturePipelineType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\LeadCapture\LeadCapturePipelineType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\LeadCapture\LeadCaptureSearchType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\LeadCapture\LeadCaptureSearchType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\LeadCapture\LeadCaptureSearchType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\LeadCapture\LeadCaptureStageType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\LeadCapture\LeadCaptureStageType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\LeadCapture\LeadCaptureStageType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\LeadCapture\LeadCaptureType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\LeadCapture\LeadCaptureType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\LeadCapture\LeadCaptureType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\LoginType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\LoginType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Media\CorrespondenceMediaType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Media\CorrespondenceMediaType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Media\DocumentMediaType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Media\DocumentMediaType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Media\HelpMediaType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Media\HelpMediaType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Media\MarketingMediaType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Media\MarketingMediaType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Media\MarketingMediaType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Media\MediaType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Media\MediaType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Message\MessageType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Message\MessageType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Message\MessageType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Model\BoardSearchClinicFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Model\BoardSearchClinicFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Model\BoardSearchClinicFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Model\CalendarSearchFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Model\CalendarSearchFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Model\CalendarSearchFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Model\ImportCSVType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Model\ImportCSVType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Model\ImportZipType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Model\ImportZipType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Model\ReportSearchClinicFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Model\ReportSearchClinicFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Model\ReportSearchClinicFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Organisation\CustomerSetting\CustomerSettingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Organisation\CustomerSetting\CustomerSettingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Organisation\CustomerSetting\CustomerSettingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Organisation\OrganisationType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Organisation\OrganisationType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Organisation\OrganisationType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Organisation\SearchFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Organisation\SearchFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Organisation\SearchFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\ActivePhotoType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\ActivePhotoType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\ActivePhotoType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Correspondence\CorrespondenceType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Correspondence\CorrespondenceType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Correspondence\CorrespondenceType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Correspondence\CorrespondenceUploadType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Correspondence\CorrespondenceUploadType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Correspondence\CorrespondenceUploadType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Correspondence\MessageTemplateType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Correspondence\MessageTemplateType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Correspondence\MessageTemplateType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\CreditNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\CreditNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\DocumentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\DocumentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\DocumentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\EditInvoiceNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\EditInvoiceNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\EditInvoiceNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\EditInvoiceType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\EditInvoiceType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\EditInvoiceType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\FormType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\FormType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\FormType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\GiftVoucherType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\GiftVoucherType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Invoice\BaseItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Invoice\BaseItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Invoice\BaseItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Invoice\InvoiceItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Invoice\InvoiceItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Invoice\InvoiceItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Invoice\RefundConnectEType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Invoice\RefundConnectEType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Invoice\RefundConnectEType" now to avoid errors or add an explicit @return annotation to suppress this message.
{closure:{closure:App\Form\Type\Patient\Invoice\RefundType::buildForm():115}:322}(): Implicitly marking parameter $entity as nullable is deprecated, the explicit nullable type must be used instead
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Invoice\RefundType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Invoice\RefundType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Invoice\RefundType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\InvoiceType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\InvoiceType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\InvoiceType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Note\AdditionalNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Note\AdditionalNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Note\AdditionalNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Note\AudioNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Note\AudioNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Note\AudioNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Note\ConsultationNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Note\ConsultationNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Note\ConsultationNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Note\NoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Note\NoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Note\NoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Note\PatientType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Note\PatientType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Note\PatientType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Note\TreatmentNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Note\TreatmentNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Note\TreatmentNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Note\TreatmentOutcomeNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Note\TreatmentOutcomeNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Note\TreatmentOutcomeNoteType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PatientAppointmentTabSearchType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PatientAppointmentTabSearchType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PatientAppointmentTabSearchType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PatientSearchType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PatientSearchType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Payment\HandpointPOSType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Payment\HandpointPOSType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Payment\HandpointPOSType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Payment\HandpointType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Payment\HandpointType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Payment\HandpointType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Payment\KindType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Payment\KindType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Payment\KindType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Payment\PaymentsenseConnectType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Payment\PaymentsenseConnectType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Payment\PaymentsenseConnectType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Payment\PaymentsensePOSTerminalsType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Payment\PaymentsensePOSTerminalsType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Payment\PaymentsensePOSTerminalsType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Payment\PaymentsensePOSType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Payment\PaymentsensePOSType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Payment\PaymentsensePOSType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Payment\TerminalType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Payment\TerminalType" now to avoid errors or add an explicit @return annotation to suppress this message.
{closure:{closure:App\Form\Type\Patient\PaymentType::buildForm():38}:198}(): Implicitly marking parameter $entity as nullable is deprecated, the explicit nullable type must be used instead
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PaymentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PaymentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PaymentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PhotoType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PhotoType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PhotoType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PostAptFormSent\FormFileType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PostAptFormSent\FormFileType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PostAptFormSent\PatientType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PostAptFormSent\PatientType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PostAptFormSent\QuestionType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PostAptFormSent\QuestionType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PostAptFormSent\QuestionnaireType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PostAptFormSent\QuestionnaireType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PostAptFormSentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PostAptFormSentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PostAptFormSentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Prepay\PrepayTreatmentItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Prepay\PrepayTreatmentItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\Prepay\PrepayTreatmentItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
{closure:App\Form\Type\Patient\PrepayType::buildForm():249}(): Implicitly marking parameter $entity as nullable is deprecated, the explicit nullable type must be used instead
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PrepayType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\PrepayType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\SearchAjaxFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\SearchAjaxFilterType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\SearchWaitingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\SearchWaitingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\SurveySent\FormFileType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\SurveySent\FormFileType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\SurveySent\PatientType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\SurveySent\PatientType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\SurveySent\QuestionType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\SurveySent\QuestionType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\SurveySent\QuestionnaireType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\SurveySent\QuestionnaireType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\SurveySentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\SurveySentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\SurveySentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\TreatmentPhotoType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\TreatmentPhotoType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\TreatmentPhotoType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\TreatmentPhotoUsedProductType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\TreatmentPhotoUsedProductType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\TreatmentPhotoUsedProductType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\TreatmentPlanType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\TreatmentPlanType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\TreatmentPlanType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\TreatmentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\TreatmentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\TreatmentType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\UsedMembershipType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\UsedMembershipType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Patient\UsedMembershipType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Person\AdminSupportType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Person\AdminSupportType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Person\AdminSupportType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Person\PatientType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Person\PatientType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Person\PatientType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Person\ProfileType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Person\ProfileType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Person\ProfileType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Person\ReportSettingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Person\ReportSettingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Person\ReportSettingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Person\SettingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Person\SettingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Person\SettingType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Person\SuperClinicAdminType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Person\SuperClinicAdminType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Person\SuperClinicAdminType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Person\UserType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Person\UserType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Person\UserType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\PriceTier\AddonType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\PriceTier\AddonType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\PriceTier\PriceTierType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\PriceTier\PriceTierType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\PriceTier\PriceTiersGroupType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\PriceTier\PriceTiersGroupType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\PriceTier\PromoCodeType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\PriceTier\PromoCodeType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\RecoveryType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\RecoveryType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\RecoveryType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\RegistrationType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\RegistrationType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::buildForm()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Waiting\ItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::configureOptions()" might add "void" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Waiting\ItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Symfony\Component\Form\AbstractType::getBlockPrefix()" might add "string" as a native return type declaration in the future. Do the same in child class "App\Form\Type\Waiting\ItemType" now to avoid errors or add an explicit @return annotation to suppress this message.
App\Import\ImportConsentForms::generateMedia(): Implicitly marking parameter $oldMedia as nullable is deprecated, the explicit nullable type must be used instead
App\Import\ImportConsentForms::generateMedia(): Implicitly marking parameter $creatingDate as nullable is deprecated, the explicit nullable type must be used instead
App\Import\ImportPhotos::generateMedia(): Implicitly marking parameter $oldMediaPhoto as nullable is deprecated, the explicit nullable type must be used instead
App\Import\ImportPhotos::generateMedia(): Implicitly marking parameter $oldMediaThumbnail as nullable is deprecated, the explicit nullable type must be used instead
App\Import\ImportQuestionnaires::generateMedia(): Implicitly marking parameter $oldMedia as nullable is deprecated, the explicit nullable type must be used instead
App\Import\ImportQuestionnaires::generateMedia(): Implicitly marking parameter $creatingDate as nullable is deprecated, the explicit nullable type must be used instead
App\Model\Calendar\DraggableEvent::setPractitioner(): Implicitly marking parameter $practitioner as nullable is deprecated, the explicit nullable type must be used instead
App\Model\Calendar\DraggableEvent::setRoom(): Implicitly marking parameter $room as nullable is deprecated, the explicit nullable type must be used instead
App\Model\Calendar\DraggableEvent::setTreatment(): Implicitly marking parameter $treatment as nullable is deprecated, the explicit nullable type must be used instead
App\Model\Calendar\DraggableEvent::setStatus(): Implicitly marking parameter $status as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Appointments::getDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Appointments::generateTableByDataReport(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Appointments::generateTableByDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Interfaces\ReportInterface::getDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Interfaces\ReportInterface::generateTableByDataReport(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Interfaces\ReportInterface::generateTableByDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Billings::getDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Billings::generateTableByDataReport(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Billings::generateTableByDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Cancellations::getDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Cancellations::generateTableByDataReport(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Cancellations::generateTableByDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\CommissionReport::getDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\CommissionReport::generateTableByDataReport(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\CommissionReport::generateTableByDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\ConsentCompletionTypePeriod\ConsentCompletionDay::getFormat(): Implicitly marking parameter $date as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\ConsentCompletionTypePeriod\ConsentCompletionDay::getDateStart(): Implicitly marking parameter $date as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\ConsentCompletionTypePeriod\ConsentCompletionDay::getDateEnd(): Implicitly marking parameter $date as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\ConsentCompletionTypePeriod\ConsentCompletionMonth::getFormat(): Implicitly marking parameter $date as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\ConsentCompletionTypePeriod\ConsentCompletionMonth::getDateStart(): Implicitly marking parameter $date as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\ConsentCompletionTypePeriod\ConsentCompletionMonth::getDateEnd(): Implicitly marking parameter $date as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\ConsentCompletionTypePeriod\ConsentCompletionWeek::getFormat(): Implicitly marking parameter $date as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\ConsentCompletionTypePeriod\ConsentCompletionWeek::getDateStart(): Implicitly marking parameter $date as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\ConsentCompletionTypePeriod\ConsentCompletionWeek::getDateEnd(): Implicitly marking parameter $date as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\ConsentCompletionTypePeriod\ConsentCompletionYear::getFormat(): Implicitly marking parameter $date as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\ConsentCompletionTypePeriod\ConsentCompletionYear::getDateStart(): Implicitly marking parameter $date as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\ConsentCompletionTypePeriod\ConsentCompletionYear::getDateEnd(): Implicitly marking parameter $date as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Dob::getDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Dob::generateTableByDataReport(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Dob::generateTableByDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\EmailOpenRate::getDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\EmailOpenRate::generateTableByDataReport(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\EmailOpenRate::generateTableByDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Invoice::getDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Invoice::generateTableByDataReport(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Invoice::generateTableByDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\LastAppointments::getDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\LastAppointments::generateTableByDataReport(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\LastAppointments::generateTableByDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\NewPatients::getDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\NewPatients::generateTableByDataReport(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\NewPatients::generateTableByDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Patients::getDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Patients::generateTableByDataReport(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Patients::generateTableByDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\PatientsWithCoursesAndNoFutureAppointments::getDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\PatientsWithCoursesAndNoFutureAppointments::generateTableByDataReport(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\PatientsWithCoursesAndNoFutureAppointments::generateTableByDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\PhotoConsentReport::getDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\PhotoConsentReport::generateTableByDataReport(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\PhotoConsentReport::generateTableByDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Practitioner::getDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Practitioner::generateTableByDataReport(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Practitioner::generateTableByDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\PractitionerOccupancyReport::getDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\PractitionerOccupancyReport::generateTableByDataReport(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\PractitionerOccupancyReport::generateTableByDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Prospects::getDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Prospects::generateTableByDataReport(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Prospects::generateTableByDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\ProspectsConverting::getDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\ProspectsConverting::generateTableByDataReport(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\ProspectsConverting::generateTableByDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\RetentionReport::getDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\RetentionReport::generateTableByDataReport(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\RetentionReport::generateTableByDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\TopSpendingPatients::getDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\TopSpendingPatients::generateTableByDataReport(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\TopSpendingPatients::generateTableByDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\TreatmentInterestedIn::getDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\TreatmentInterestedIn::generateTableByDataReport(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\TreatmentInterestedIn::generateTableByDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\TreatmentRisk::getDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\TreatmentRisk::generateTableByDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Treatments::getDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Treatments::generateTableByDataReport(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Model\CustomReports\Treatments::generateTableByDataReport(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
Return type of App\Model\MailChimp\BatchOperation::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Method "JsonSerializable::jsonSerialize()" might add "mixed" as a native return type declaration in the future. Do the same in implementation "App\Model\MailChimp\BatchOperation" now to avoid errors or add an explicit @return annotation to suppress this message.
Return type of App\Model\MailChimp\BatchRequest::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Method "JsonSerializable::jsonSerialize()" might add "mixed" as a native return type declaration in the future. Do the same in implementation "App\Model\MailChimp\BatchRequest" now to avoid errors or add an explicit @return annotation to suppress this message.
Return type of App\Model\MailChimp\MailChimpWebHooksSources::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Method "JsonSerializable::jsonSerialize()" might add "mixed" as a native return type declaration in the future. Do the same in implementation "App\Model\MailChimp\MailChimpWebHooksSources" now to avoid errors or add an explicit @return annotation to suppress this message.
Return type of App\Model\MailChimp\MemberMergeFields::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Method "JsonSerializable::jsonSerialize()" might add "mixed" as a native return type declaration in the future. Do the same in implementation "App\Model\MailChimp\MemberMergeFields" now to avoid errors or add an explicit @return annotation to suppress this message.
App\Report\ItemReportResult::setTreatmentCategory(): Implicitly marking parameter $treatmentCategory as nullable is deprecated, the explicit nullable type must be used instead
App\Report\ItemReportResult::setPriceList(): Implicitly marking parameter $priceList as nullable is deprecated, the explicit nullable type must be used instead
App\Report\ItemReportResult::setProduct(): Implicitly marking parameter $product as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\AppointmentLeadRepository::getActualEvents(): Implicitly marking parameter $clinic as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Appointment\GoogleEventRepository::findNumberAppointmentsDateRange(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Appointment\GoogleEventRepository::findNumberAppointmentsDateRangeForCancellation(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Appointment\GoogleEventRepository::selectNumberAppointmentsDateRange(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Appointment\GoogleEventRepository::selectNumberAppointmentsDateRange(): Implicitly marking parameter $typeReport as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Appointment\GoogleEventRepository::selectNumberAppointmentsDateRange(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Appointment\GoogleEventRepository::countAllRecordsDetailLastAppointment(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Appointment\GoogleEventRepository::countAllRecordsDetail(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Appointment\GoogleEventRepository::getActualEvents(): Implicitly marking parameter $appointment as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Appointment\GoogleEventRepository::getActualEvents(): Implicitly marking parameter $clinic as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Appointment\GoogleEventRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Appointment\GoogleEventRepository::getNumberBookedEventsByPractitioner(): Implicitly marking parameter $event as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Appointment\GoogleEventRepository::getNumberBookedOnlyBlockersEventsByPractitioner(): Implicitly marking parameter $event as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Appointment\GoogleEventRepository::getNumberBookedEventsByRoom(): Implicitly marking parameter $event as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Appointment\GoogleEventRepository::getNumberBookedEventsByEquipments(): Implicitly marking parameter $event as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Appointment\GoogleEventRepository::qbForCheckBusy(): Implicitly marking parameter $event as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Appointment\GoogleEventRepository::findPatientAppointmentCancelled(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\AppointmentRepository::findAppointmentsByPatient(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\AppointmentRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\AppointmentRepository::findPatientCancelledAppointments(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\AppointmentRepository::findPatientCancelledAppointments(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\AppointmentRepository::findLastAppointmentOfAllPatient(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\BlockerReasonRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\ClinicRepository::selectActiveClinicByUser(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\ClinicRepository::findActiveClinicBySuperAdmin(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\ClinicRepository::countAllRecords(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\ClinicRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\DiscountReasonRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\DocumentCategoryRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\EquipmentRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\FormFileRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\GocardlessCustomerRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\LicenseRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\MarketingRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\MeetingRepository::findAppointmentsByPatient(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\MeetingRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\MeetingRepository::getActualEvents(): Implicitly marking parameter $clinic as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Person\ClinicUserRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\PolicyRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Questionaire\AnswerRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Questionaire\QuestionRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Questionaire\QuestionaireRepository::selectAnsweredQuestionnaireByClinic(): Implicitly marking parameter $questionaire as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Questionaire\QuestionaireRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\ReferralGiftRepository::findAllForAdmin(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\ReferralInvitationRepository::loadUserReferralRewardsProgressSummary(): Implicitly marking parameter $currency as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\ReferralInvitationRepository::findByReferrer(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\ReferralInvitationRepository::getReferralRewards(): Implicitly marking parameter $currency as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\RoomRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Stock\AdjustStockRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Stock\GoodsReceivedRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Stock\HistoryRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Stock\ItemGoodsReceivedRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Stock\PriceListRepository::countAllRecords(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Stock\PriceListRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Stock\ProductRepository::countAllRecords(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Stock\ProductRepository::countAllRecordsDetail(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Stock\ProductRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Stock\TreatmentClinicRepository::countAllRecords(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Clinic\Stock\TreatmentClinicRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\LeadCapture\LeadCaptureRepository::findProspectsByClinicId(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\LeadCapture\LeadCaptureRepository::findProspectsByClinicId(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\LeadCapture\LeadCaptureRepository::findProspectsByClinicId(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\LeadCapture\LeadCaptureRepository::findConversionProspectsByClinicId(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\LeadCapture\LeadCaptureRepository::findProspectAdditionalColumnsByClinicId(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\LeadCapture\LeadCaptureRepository::findProspectAdditionalColumnsByClinicId(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\LeadCapture\LeadCaptureRepository::countAllRecordsDetail(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\LeadCapture\LeadCaptureRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\LeadCapture\LeadCaptureRepository::findProspectWithClinicUserId(): Implicitly marking parameter $clinicUser as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\BaseInvoiceRepository::selectBillingByFilter(): Implicitly marking parameter $typeInvoice as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\BaseInvoiceRepository::selectBilling(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\BaseInvoiceRepository::selectBilling(): Implicitly marking parameter $typeInvoice as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\BaseInvoiceRepository::selectBilling(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\BaseInvoiceRepository::selectInvoicesReports(): Implicitly marking parameter $typeInvoice as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\BaseInvoiceRepository::selectInvoicesReports(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\BaseInvoiceRepository::countAllRecordsDetail(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\CreditNoteRepository::countAllRecords(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\CreditNoteRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\DocumentRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\FormRepository::findData(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\FormRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\GiftVoucherRepository::countAllRecordsDetail(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\Invoice\HistoryRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\Invoice\ItemRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\Invoice\RefundRepository::countAllRecordsDetail(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\Invoice\RefundRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\InvoiceRepository::countAllRecords(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\InvoiceRepository::selectInvoicesForTable(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\InvoiceRepository::countAllRecordsDetail(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\InvoiceRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\Note\AdditionalNoteRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\Note\AudioNoteRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\Note\ConsultationNoteRepository::findConsultationNotesByPatient(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\Note\ConsultationNoteRepository::findPractitionerFromConsultationNotesByPatient(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\Note\ConsultationNoteRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\Note\MemoryJogRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\Note\NoteRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\Note\TreatmentNoteRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\Payment\KindRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\PaymentRepository::countAllRecordsDetail(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\PaymentRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\PhotoRepository::selectConsultationPhotosByPatient(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\PhotoRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\PhotoRepository::findDataExportQuery(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\PhotoRepository::findDataExportCsv(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\PrepayRepository::countAllRecords(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\PrepayRepository::countAllRecordsDetail(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\PrepayRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\PrepayRepository::selectClinicPrepay(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\Questionnaire\QuestionnairePDFRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\SketchRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\TreatmentPlanEntryRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\TreatmentPlanRepository::findTreatmentPlansByPatient(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Patient\TreatmentPlanRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Person\Patient\BalanceRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Person\PatientRepository::findPatientBday(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Person\PatientRepository::findPatientBday(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Person\PatientRepository::countAllRecords(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Person\PatientRepository::countAllRecordsWithNullableCreatedBy(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Person\PatientRepository::selectPatientsForSms(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Person\PatientRepository::selectPatientsForEmail(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Person\PatientRepository::countAllRecordsDetail(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Person\PatientRepository::countAllPatientBaseVisitDetail(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Person\PatientRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Person\PatientRepository::findPatientAppointmentCancelled1(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Person\PatientRepository::findPatientLastAppointments(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Person\PatientRepository::findPatientByClinic(): Implicitly marking parameter $filter as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Person\PatientRepository::findPatientByClinic(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Person\PatientRepository::findPatientByClinic_treatmentInterestedIn(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Person\PatientRepository::getTopSpendingPatient(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Waiting\ItemRepository::countAllRecords(): Implicitly marking parameter $criteria as nullable is deprecated, the explicit nullable type must be used instead
App\Repository\Waiting\ItemRepository::findDataExport(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Security\ApplicationAuthenticator::start(): Implicitly marking parameter $authException as nullable is deprecated, the explicit nullable type must be used instead
The "App\Security\PermissionVoter::voteOnAttribute()" method will require a new "Vote|null $vote" argument in the next major version of its parent class "Symfony\Component\Security\Core\Authorization\Voter\Voter", not defining it is deprecated.
The "App\Security\UserChecker::checkPostAuth()" method will require a new "?TokenInterface $token" argument in the next major version of its interface "Symfony\Component\Security\Core\User\UserCheckerInterface", not defining it is deprecated.
App\Service\RateLimiter\RateLimiterService::__construct(): Implicitly marking parameter $redis as nullable is deprecated, the explicit nullable type must be used instead
App\Services\AppointmentService::getAppointmentsData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\AppointmentService::getAppointmentsData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\CalendarEvent\SchedulerCalendarEvents::createEvent(): Implicitly marking parameter $recurrence as nullable is deprecated, the explicit nullable type must be used instead
App\Services\CalendarEvent\SchedulerCalendarEvents::checkFreeBusyByAppointment(): Implicitly marking parameter $event as nullable is deprecated, the explicit nullable type must be used instead
App\Services\CancellationService::getCancellationsData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\CancellationService::getCancellationsData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\ConversionService::getNewPatientAppointmentsData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\ConversionService::getNewPatientAppointmentsData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\ConversionService::getProspectsData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\ConversionService::getProspectsData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\CustomReports\GenerateReportsService::getGenerateTables(): Implicitly marking parameter $page as nullable is deprecated, the explicit nullable type must be used instead
App\Services\CustomReports\GenerateReportsService::getDataReports(): Implicitly marking parameter $reportId as nullable is deprecated, the explicit nullable type must be used instead
App\Services\DeviceManager::logoutFirstUser(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead
App\Services\ExportClinicData::getData(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Services\ExportClinicData::getDataDB(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Services\ExportClinicData::getDataCSV(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Services\ExportClinicData::unlock(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Services\FinancialService::getReceiptsData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\FinancialService::getReceiptsData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\FinancialService::getNetReceiptsData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\FinancialService::getNetReceiptsData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\FinancialService::getRefundsData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\FinancialService::getRefundsData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\FinancialService::getPrepaymentsBalanceData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\FinancialService::getPrepaymentsBalanceData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\FinancialService::getReconciliationData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\FinancialService::getReconciliationData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\FinancialService::getUnpaidReportData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\FinancialService::getUnpaidReportData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\GoogleService::syncAppointment(): Implicitly marking parameter $service as nullable is deprecated, the explicit nullable type must be used instead
App\Services\GoogleService::deleteEvent(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead
App\Services\MailingListService::getMailingListData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\MailingListService::getMailingListData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PatientReferralService::getPatientReferralData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PatientReferralService::getPatientReferralData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PatientService::getRecencyData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PatientService::getRecencyData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PatientService::getFrequencyData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PatientService::getFrequencyData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PatientService::getCustomerBaseData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PatientService::getCustomerBaseData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PatientSpendingService::getAverageSpendData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PatientSpendingService::getAverageSpendData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PatientSpendingService::getPatientListByTreatmentDateData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PatientSpendingService::getPatientListByTreatmentDateData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PaymentSense\HandpointE::__construct(): Implicitly marking parameter $logger as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PaymentSense\HandpointE::directRequest(): Implicitly marking parameter $options as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PaymentSense\HandpointE::hostedRequest(): Implicitly marking parameter $options as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PaymentSense\HandpointE::prepareRequest(): Implicitly marking parameter $options as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PaymentSense\HandpointE::collectBrowserInfo(): Implicitly marking parameter $options as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PractitionerReportsService::getBillingsPerPractitionerData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PractitionerReportsService::getBillingsPerPractitionerData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PractitionerReportsService::getRevenuePerPractitionerData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PractitionerReportsService::getRevenuePerPractitionerData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PractitionerReportsService::getBillingsPerPeriodData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PractitionerReportsService::getBillingsPerPeriodData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PractitionerReportsService::getRevenuePerPeriodData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PractitionerReportsService::getRevenuePerPeriodData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PractitionerReportsService::getBillingsPerCoordinatorData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PractitionerReportsService::getBillingsPerCoordinatorData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\PriceTiersService::create(): Implicitly marking parameter $addons as nullable is deprecated, the explicit nullable type must be used instead
App\Services\Referral\FirstPromoterClient::makeRequest(): Implicitly marking parameter $data as nullable is deprecated, the explicit nullable type must be used instead
App\Services\RetentionService::getRetentionData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\RetentionService::getRetentionData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\SmsMessagesService::getSmsMessagesData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\SmsMessagesService::getSmsMessagesData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\SmsService::sendSMSCampaign(): Optional parameter $type declared before required parameter $campainUserId is implicitly treated as a required parameter
App\Services\TerminalService::getTerminalsEndOfDayData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\TerminalService::getTerminalsEndOfDayData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\VoucherService::getVouchersData(): Implicitly marking parameter $customStart as nullable is deprecated, the explicit nullable type must be used instead
App\Services\VoucherService::getVouchersData(): Implicitly marking parameter $customEnd as nullable is deprecated, the explicit nullable type must be used instead
App\Services\Xero\XeroSyncWorker::queue(): Implicitly marking parameter $time as nullable is deprecated, the explicit nullable type must be used instead
Method "Twig\Extension\ExtensionInterface::getFilters()" might add "array" as a native return type declaration in the future. Do the same in implementation "App\Twig\AppExtension" now to avoid errors or add an explicit @return annotation to suppress this message.
Method "Twig\Extension\ExtensionInterface::getFunctions()" might add "array" as a native return type declaration in the future. Do the same in implementation "App\Twig\AppExtension" now to avoid errors or add an explicit @return annotation to suppress this message.
The "App\Voters\AppVoter::voteOnAttribute()" method will require a new "Vote|null $vote" argument in the next major version of its parent class "Symfony\Component\Security\Core\Authorization\Voter\Voter", not defining it is deprecated.
The "App\Voters\OrganisationVoter::voteOnAttribute()" method will require a new "Vote|null $vote" argument in the next major version of its parent class "Symfony\Component\Security\Core\Authorization\Voter\Voter", not defining it is deprecated.
The "App\Voters\AdditionalNoteVoter::voteOnAttribute()" method will require a new "Vote|null $vote" argument in the next major version of its parent class "Symfony\Component\Security\Core\Authorization\Voter\Voter", not defining it is deprecated.
The "App\Voters\ApiVoter::voteOnAttribute()" method will require a new "Vote|null $vote" argument in the next major version of its parent class "Symfony\Component\Security\Core\Authorization\Voter\Voter", not defining it is deprecated.
The "App\Voters\AppointmentVoter::voteOnAttribute()" method will require a new "Vote|null $vote" argument in the next major version of its parent class "Symfony\Component\Security\Core\Authorization\Voter\Voter", not defining it is deprecated.
The "App\Voters\ClinicsVoter::voteOnAttribute()" method will require a new "Vote|null $vote" argument in the next major version of its parent class "Symfony\Component\Security\Core\Authorization\Voter\Voter", not defining it is deprecated.
The "App\Voters\ConsultationNoteVoter::voteOnAttribute()" method will require a new "Vote|null $vote" argument in the next major version of its parent class "Symfony\Component\Security\Core\Authorization\Voter\Voter", not defining it is deprecated.
The "App\Voters\InvoiceVoter::voteOnAttribute()" method will require a new "Vote|null $vote" argument in the next major version of its parent class "Symfony\Component\Security\Core\Authorization\Voter\Voter", not defining it is deprecated.
The "App\Voters\LeadCaptureVoter::voteOnAttribute()" method will require a new "Vote|null $vote" argument in the next major version of its parent class "Symfony\Component\Security\Core\Authorization\Voter\Voter", not defining it is deprecated.
The "App\Voters\MediaVoter::voteOnAttribute()" method will require a new "Vote|null $vote" argument in the next major version of its parent class "Symfony\Component\Security\Core\Authorization\Voter\Voter", not defining it is deprecated.
The "App\Voters\NotConvertReasonVoter::voteOnAttribute()" method will require a new "Vote|null $vote" argument in the next major version of its parent class "Symfony\Component\Security\Core\Authorization\Voter\Voter", not defining it is deprecated.
The "App\Voters\PatientVoter::voteOnAttribute()" method will require a new "Vote|null $vote" argument in the next major version of its parent class "Symfony\Component\Security\Core\Authorization\Voter\Voter", not defining it is deprecated.
The "App\Voters\QuestionaireVoter::voteOnAttribute()" method will require a new "Vote|null $vote" argument in the next major version of its parent class "Symfony\Component\Security\Core\Authorization\Voter\Voter", not defining it is deprecated.
The "App\Voters\SuperAdminVoter::voteOnAttribute()" method will require a new "Vote|null $vote" argument in the next major version of its parent class "Symfony\Component\Security\Core\Authorization\Voter\Voter", not defining it is deprecated.
The "App\Voters\TreatmentNoteVoter::voteOnAttribute()" method will require a new "Vote|null $vote" argument in the next major version of its parent class "Symfony\Component\Security\Core\Authorization\Voter\Voter", not defining it is deprecated.
The "App\Voters\TreatmentVoter::voteOnAttribute()" method will require a new "Vote|null $vote" argument in the next major version of its parent class "Symfony\Component\Security\Core\Authorization\Voter\Voter", not defining it is deprecated.
App\Entity\Person\User::getClinicRole(): Implicitly marking parameter $editUser as nullable is deprecated, the explicit nullable type must be used instead
Return type of App\Entity\Person\User::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Method "JsonSerializable::jsonSerialize()" might add "mixed" as a native return type declaration in the future. Do the same in implementation "App\Entity\Person\User" now to avoid errors or add an explicit @return annotation to suppress this message.
App\Entity\Clinic\Clinic::getStrReplacedTAndC(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
Return type of App\Entity\Clinic\Clinic::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Method "JsonSerializable::jsonSerialize()" might add "mixed" as a native return type declaration in the future. Do the same in implementation "App\Entity\Clinic\Clinic" now to avoid errors or add an explicit @return annotation to suppress this message.
App\Entity\Person\AdminSupport implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary)
Method "JsonSerializable::jsonSerialize()" might add "mixed" as a native return type declaration in the future. Do the same in implementation "App\Entity\Person\AdminSupport" now to avoid errors or add an explicit @return annotation to suppress this message.
App\Entity\Clinic\Appointment\GoogleEvent::setStatusDaySheet(): Implicitly marking parameter $statusDaySheet as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Clinic\Appointment\GoogleEvent::setRoom(): Implicitly marking parameter $room as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Clinic\Appointment\GoogleEvent::setTreatmentClinic(): Implicitly marking parameter $treatment as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Clinic\BlockerReason::setClinic(): Implicitly marking parameter $clinic as nullable is deprecated, the explicit nullable type must be used instead
Return type of App\Entity\Clinic\BlockerReason::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
App\Entity\Clinic\Campaign\Campaign::setClinic(): Implicitly marking parameter $clinic as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Clinic\DiscountReason::setClinic(): Implicitly marking parameter $clinic as nullable is deprecated, the explicit nullable type must be used instead
Return type of App\Entity\Clinic\DiscountReason::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
App\Entity\Clinic\DocumentCategory::setClinic(): Implicitly marking parameter $clinic as nullable is deprecated, the explicit nullable type must be used instead
Return type of App\Entity\Clinic\DocumentCategory::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
App\Entity\Clinic\EmailTemplate\EmailTemplate::setClinic(): Implicitly marking parameter $clinic as nullable is deprecated, the explicit nullable type must be used instead
Return type of App\Entity\Clinic\Equipment::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Method "JsonSerializable::jsonSerialize()" might add "mixed" as a native return type declaration in the future. Do the same in implementation "App\Entity\Clinic\Equipment" now to avoid errors or add an explicit @return annotation to suppress this message.
Return type of App\Entity\Clinic\FormFile::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Method "JsonSerializable::jsonSerialize()" might add "mixed" as a native return type declaration in the future. Do the same in implementation "App\Entity\Clinic\FormFile" now to avoid errors or add an explicit @return annotation to suppress this message.
App\Entity\Clinic\Membership\Membership::setClinic(): Implicitly marking parameter $clinic as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Clinic\NotConvertReason::setClinic(): Implicitly marking parameter $clinic as nullable is deprecated, the explicit nullable type must be used instead
Return type of App\Entity\Clinic\PatientStatus\PatientStatus::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Method "JsonSerializable::jsonSerialize()" might add "mixed" as a native return type declaration in the future. Do the same in implementation "App\Entity\Clinic\PatientStatus\PatientStatus" now to avoid errors or add an explicit @return annotation to suppress this message.
Return type of App\Entity\Clinic\Room::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Method "JsonSerializable::jsonSerialize()" might add "mixed" as a native return type declaration in the future. Do the same in implementation "App\Entity\Clinic\Room" now to avoid errors or add an explicit @return annotation to suppress this message.
App\Entity\Clinic\Stock\History::setGoodsReceived(): Implicitly marking parameter $goodsReceived as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Clinic\Stock\History::setPatient(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Clinic\Stock\History::setInvoice(): Implicitly marking parameter $invoice as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Clinic\Stock\History::setAdjustStock(): Implicitly marking parameter $adjustStock as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Clinic\Stock\History::setPractitioner(): Implicitly marking parameter $practitioner as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Clinic\Stock\PriceList::setTreatment(): Implicitly marking parameter $treatment as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Clinic\Person\ClinicUser implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary)
App\Entity\Patient\Invoice::setConsultationPractitioner(): Implicitly marking parameter $consultationPractitioner as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Patient\Invoice::setGeneratedPatientVoucher(): Implicitly marking parameter $generatedPatientVoucher as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Patient\Invoice::setConsultationNote(): Implicitly marking parameter $consultationNote as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Patient\BaseInvoice::setClinic(): Implicitly marking parameter $clinic as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\LeadCapture\LeadCapture::setClinic(): Implicitly marking parameter $clinic as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Person\SuperClinicAdmin::setCurrentClinic(): Implicitly marking parameter $currentClinic as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Person\SuperClinicAdmin implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary)
Method "JsonSerializable::jsonSerialize()" might add "mixed" as a native return type declaration in the future. Do the same in implementation "App\Entity\Person\SuperClinicAdmin" now to avoid errors or add an explicit @return annotation to suppress this message.
App\Entity\Person\Patient::getStatuses(): Implicitly marking parameter $clinic as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Person\Patient::setParent(): Implicitly marking parameter $parent as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Person\Patient implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary)
Return type of App\Entity\Patient\Correspondence\MessageTemplate::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Method "JsonSerializable::jsonSerialize()" might add "mixed" as a native return type declaration in the future. Do the same in implementation "App\Entity\Patient\Correspondence\MessageTemplate" now to avoid errors or add an explicit @return annotation to suppress this message.
App\Entity\Patient\Document::setPatient(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Patient\Document::setMedia(): Implicitly marking parameter $media as nullable is deprecated, the explicit nullable type must be used instead
Return type of App\Entity\Patient\Document::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
App\Entity\Patient\Payment::setPrepayment(): Implicitly marking parameter $prepayment as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Patient\Payment::setPrepayTreatmentItem(): Implicitly marking parameter $prepayTreatmentItem as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Patient\Invoice\BaseItem::setPriceList(): Implicitly marking parameter $priceList as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Patient\Invoice\BaseItem::setVat(): Implicitly marking parameter $vat as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Patient\Prepay::setTreatment(): Implicitly marking parameter $treatment as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Patient\Prepay::setConsultationPractitioner(): Implicitly marking parameter $consultationPractitioner as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Patient\TreatmentPlan::setPatient(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Patient\TreatmentPlan::setClinicUser(): Implicitly marking parameter $clinicUser as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Patient\TreatmentPlan::setSuperClinicAdmin(): Implicitly marking parameter $superClinicAdmin as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Patient\TreatmentPhoto\TreatmentPhotoUsedProduct::setItemGoodsReceived(): Implicitly marking parameter $itemGoodsReceived as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Patient\TreatmentPhoto\TreatmentPhotoUsedProduct::setProduct(): Implicitly marking parameter $product as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Waiting\Item::setPatient(): Implicitly marking parameter $patient as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Waiting\Item::setPractitioner(): Implicitly marking parameter $practitioner as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\Event::setQuestionaire(): Implicitly marking parameter $questionaire as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\AppointmentLead::setClinic(): Implicitly marking parameter $clinic as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\AppointmentLead::setLeadCapture(): Implicitly marking parameter $leadCapture as nullable is deprecated, the explicit nullable type must be used instead
App\Entity\AppointmentLead::setCustomFormData(): Implicitly marking parameter $customFormData as nullable is deprecated, the explicit nullable type must be used instead
Deprecated: App\EventListener\DoctrineExtensionSubscriber::__construct(): Optional parameter $blameableListener declared before required parameter $tokenStorage is implicitly treated as a required parameter
Deprecated: App\EventListener\RateLimitSubscriber::__construct(): Implicitly marking parameter $tokenStorage as nullable is deprecated, the explicit nullable type must be used instead
Deprecated: App\Service\RateLimiter\RateLimiterService::__construct(): Implicitly marking parameter $redis as nullable is deprecated, the explicit nullable type must be used instead
Deprecated: App\Services\DeviceManager::logoutFirstUser(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead