package dto_astrologer

type VerifyOTPResponse struct {
	UserID uint   `json:"user_id"`
	Status string `json:"status"`

	// Verification state and routing, so the app knows whether this call was the
	// one that completed the pair. Token and RefreshToken are set only then.
	MobileVerified   bool `json:"mobile_verified"`
	EmailVerified    bool `json:"email_verified"`
	CanCreateProfile bool `json:"can_create_profile"`

	// token, refresh_token and next_screen are always present, empty until this
	// call is the one that completes the pair. They were omitempty here but not
	// on the email verify's response, so the two endpoints handed a client two
	// different shapes for the same situation.
	Token        string `json:"token"`
	RefreshToken string `json:"refresh_token"`
	NextScreen   string `json:"next_screen"`

	PendingStep      int    `json:"pending_step,omitempty"`
	PendingStepTitle string `json:"pending_step_title,omitempty"`
}