Skip to content
This repository was archived by the owner on Jan 4, 2023. It is now read-only.

Respect both no_reserve and reserve_unknown as potential reserve statuses #615

Description

@sweir27

This is related to: artsy/eigen#1835

Basically, in places like here:

enum ReserveStatus: String {
case ReserveNotMet = "reserve_not_met"
case NoReserve = "no_reserve"
case ReserveMet = "reserve_met"
var reserveNotMet: Bool {
return self == .ReserveNotMet
}
static func initOrDefault (rawValue: String?) -> ReserveStatus {
return ReserveStatus(rawValue: rawValue ?? "") ?? .NoReserve
}
}
we want to assume that gravity could return no_reserve or reserve_unknown as a SaleArtwork.reserve_status (and both should be treated the same way we treat NoReserve today.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions