TutorProfileDisplay class
Constructors
-
TutorProfileDisplay({int? id, required UserRetrival user, int? tutorProfileId, String? experience, int? experienceYears, String? address, String? dbsNumber, String? video, String? videoLink, bool? inPersonTutoring, bool? onlineTutoring, String? personalityType, bool? profilePhotoRejected, int numReviews = 0, List<TutorSubject> subjects = const [], TutorSubject? selectedSubject, required String photo, bool? isDbsChecked, bool? isDbsCompleted, List<TutorQualification> qualifications = const [], bool? hasSkype, bool? metInPerson, List<String> coverageNames = const [], int rating = 0, String? responseTimeDisplay, String? postcode, String? slug, bool? isSuperTutor, int? numFiveStarReviews, int? numExcellentReviews, int? numProfileViews, String? tagline, String? hasNumberOfViewsBadge, bool? isLive, List<String> completedSections = const [], List<String> incompleteSections = const [], bool? profileSubmitted, bool? isFeatured, bool? enableTrial, bool? enableInstant, int? school, String schoolName = '', Country? country, bool? hasStripeAccount, List<TutorAvailability> availability = const [], List<TutorTimeOff> timeOff = const [], required String userTimezone, bool? isTrialed})
-
Returns a new TutorProfileDisplay instance.
Properties
-
address
↔ String?
-
getter/setter pair
-
availability
↔ List<TutorAvailability>
-
getter/setter pair
-
getter/setter pair
-
completedSections
↔ List<String>
-
getter/setter pair
-
country
↔ Country?
-
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
-
coverageNames
↔ List<String>
-
getter/setter pair
-
dbsNumber
↔ String?
-
getter/setter pair
-
enableInstant
↔ 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
-
enableTrial
↔ 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
-
experience
↔ String?
-
getter/setter pair
-
experienceYears
↔ int?
-
Minimum value: -2147483648
Maximum value: 2147483647
getter/setter pair
-
hashCode
→ int
-
The hash code for this object.
no setteroverride
-
hasNumberOfViewsBadge
↔ 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
-
hasSkype
↔ 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
-
hasStripeAccount
↔ 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
-
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
-
incompleteSections
↔ List<String>
-
getter/setter pair
-
inPersonTutoring
↔ 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
-
isDbsChecked
↔ 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
-
isDbsCompleted
↔ bool?
-
Checks wether a tutor has its DBS section fully completed file uploaded and dbs number.
getter/setter pair
-
isFeatured
↔ 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
-
isLive
↔ 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
-
isSuperTutor
↔ 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
-
isTrialed
↔ 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
-
metInPerson
↔ 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
-
numExcellentReviews
↔ int?
-
Minimum value: 0
Maximum value: 2147483647
getter/setter pair
-
numFiveStarReviews
↔ int?
-
Minimum value: 0
Maximum value: 2147483647
getter/setter pair
-
numProfileViews
↔ int?
-
Minimum value: 0
Maximum value: 2147483647
getter/setter pair
-
numReviews
↔ int
-
getter/setter pair
-
onlineTutoring
↔ 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
-
personalityType
↔ 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
-
photo
↔ String
-
getter/setter pair
-
postcode
↔ String?
-
getter/setter pair
-
profilePhotoRejected
↔ 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
-
profileSubmitted
↔ 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
-
qualifications
↔ List<TutorQualification>
-
getter/setter pair
-
rating
↔ int
-
getter/setter pair
-
responseTimeDisplay
↔ String?
-
getter/setter pair
-
runtimeType
→ Type
-
A representation of the runtime type of the object.
no setterinherited
-
school
↔ int?
-
getter/setter pair
-
schoolName
↔ String
-
getter/setter pair
-
selectedSubject
↔ TutorSubject?
-
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
-
slug
↔ 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
-
subjects
↔ List<TutorSubject>
-
getter/setter pair
-
tagline
↔ String?
-
getter/setter pair
-
timeOff
↔ List<TutorTimeOff>
-
getter/setter pair
-
tutorProfileId
↔ 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
-
user
↔ UserRetrival
-
getter/setter pair
-
userTimezone
↔ String
-
getter/setter pair
-
video
↔ String?
-
getter/setter pair
-
videoLink
↔ 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