PatchedBooking class

Constructors

PatchedBooking({int? id, User? customer, User? tutor, TutorFeedback? tutorFeedback, CustomerFeedback? customerFeedback, int? chat, String? cancellationPeriodHours, bool? canCancelCustomer, bool? hasCancellationPenalty, DateTime? paymentHoldsAt, int? paymentAmountInCents, String? feedbackId, SimpleSubjectLevel? subject, DateTime? created, DateTime? modified, DateTime? deletedAt, bool? isTutorPaid, bool? isAcceptedByCustomer, bool? isAcceptedByTutor, bool? isRejectedByCustomer, bool? isRejectedByTutor, String? location, DateTime? acceptanceChangedAt, DateTime? cancelledAt, bool? cancelledByCustomer, DateTime? confirmedAt, ConfirmedStatusEnum? confirmedStatus, CustomerFeedbackStatusEnum? customerFeedbackStatus, String? customerFeedbackNotes, DateTime? customerFeedbackCreatedAt, int? customerFeedbackRating, bool? customerFeedbackExcellent, String? tutorFeedbackNotes, DateTime? tutorFeedbackCreatedAt, int? tutorFeedbackRating, bool? showCustomerFeedbackOnSite, DateTime? startTime, DateTime? endTime, String? customerToken, String? tutorToken, bool? feedbackRequired, bool? isTrialCall, bool? finishedNotificationsSent, bool? reconfirmingNotificationsSent, String? cancelReason, bool? isCustomerRead, bool? isTutorRead, int? rescheduleCountByCustomer, int? rescheduleCountByTutor, int? invitation, int? cancelledBy, int? zoomMeeting})

Returns a new PatchedBooking instance.

Properties

acceptanceChangedAt ↔ DateTime?

getter/setter pair

canCancelCustomer ↔ bool?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

cancellationPeriodHours ↔ String?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

cancelledAt ↔ DateTime?

getter/setter pair

cancelledBy ↔ int?

getter/setter pair

cancelledByCustomer ↔ bool?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

cancelReason ↔ String?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

chat ↔ int?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

confirmedAt ↔ DateTime?

getter/setter pair

confirmedStatus ↔ ConfirmedStatusEnum?

getter/setter pair

created ↔ DateTime?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

customer ↔ User?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

customerFeedback ↔ CustomerFeedback?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

customerFeedbackCreatedAt ↔ DateTime?

getter/setter pair

customerFeedbackExcellent ↔ bool?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

customerFeedbackNotes ↔ String?

getter/setter pair

customerFeedbackRating ↔ int?

Minimum value: -2147483648 Maximum value: 2147483647

getter/setter pair

customerFeedbackStatus ↔ CustomerFeedbackStatusEnum?

getter/setter pair

customerToken ↔ String?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

deletedAt ↔ DateTime?

getter/setter pair

endTime ↔ DateTime?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

feedbackId ↔ String?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

feedbackRequired ↔ bool?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

finishedNotificationsSent ↔ bool?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

hasCancellationPenalty ↔ bool?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

hashCode → int

The hash code for this object.

no setter, override

id ↔ int?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

invitation ↔ int?

getter/setter pair

isAcceptedByCustomer ↔ bool?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

isAcceptedByTutor ↔ bool?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

isCustomerRead ↔ bool?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

isRejectedByCustomer ↔ bool?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

isRejectedByTutor ↔ bool?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

isTrialCall ↔ bool?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

isTutorPaid ↔ bool?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

isTutorRead ↔ bool?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

location ↔ String?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

modified ↔ DateTime?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

paymentAmountInCents ↔ int?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

paymentHoldsAt ↔ DateTime?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

reconfirmingNotificationsSent ↔ bool?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

rescheduleCountByCustomer ↔ int?

Minimum value: -2147483648 Maximum value: 2147483647

getter/setter pair

rescheduleCountByTutor ↔ int?

Minimum value: -2147483648 Maximum value: 2147483647

getter/setter pair

runtimeType → Type

A representation of the runtime type of the object.

no setter, inherited

showCustomerFeedbackOnSite ↔ bool?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

startTime ↔ DateTime?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

subject ↔ SimpleSubjectLevel?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

tutor ↔ User?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

tutorFeedback ↔ TutorFeedback?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

tutorFeedbackCreatedAt ↔ DateTime?

getter/setter pair

tutorFeedbackNotes ↔ String?

getter/setter pair

tutorFeedbackRating ↔ int?

Minimum value: -2147483648 Maximum value: 2147483647

getter/setter pair

tutorToken ↔ String?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

zoomMeeting ↔ int?

getter/setter pair

Methods

noSuchMethod(Invocation invocation) → dynamic

Invoked when a nonexistent method or property is accessed.

inherited

toJson() → Map<String, dynamic>

toString() → String

A string representation of this object.

override

Operators

operator ==(Object other) → bool

The equality operator.

override

Static Methods

fromJson(dynamic value) → PatchedBooking?

Returns a new PatchedBooking instance and imports its values from value if it's a Map, null otherwise.

listFromJson(dynamic json, {bool growable = false}) → List<PatchedBooking>

mapFromJson(dynamic json) → Map<String, PatchedBooking>

mapListFromJson(dynamic json, {bool growable = false}) → Map<String, List<PatchedBooking>>

Constants

requiredKeys → const Set<String>

The list of required keys that must be present in a JSON.