You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The secondHand component of Product.Item uses canBeUsed and priceAdjustment fields denoting whether it is valid for an item to be a used product, and if so what the value of the product should be adjusted to be. These fields are currently independent, however it does not make sense for an item to have a price adjustment if the item should be be values as a used item.
Therefore the priceAdjustment field should only be enabled when the canBeUsed field is set to true.
Change the secondHand component to be a custom component
Link the canBeUsed and priceAdjustment fields to have a dependency
Ensure the link from the Product.PriceAdjustment component to the product.item collection is maintained
Hey! Seems like a decent starting point for me. Can I take this up?
I will look into the steps and list them out, and maybe someone can make sure they're the correct steps to take 😄
Correct me if I'm wrong, but this looks like it's already done? I see a bunch of commits made right after the creation of this issue, that seem to do what is described here 👀
The secondHand component of Product.Item uses
canBeUsed
andpriceAdjustment
fields denoting whether it is valid for an item to be a used product, and if so what the value of the product should be adjusted to be. These fields are currently independent, however it does not make sense for an item to have a price adjustment if the item should be be values as a used item.Therefore the
priceAdjustment
field should only be enabled when thecanBeUsed
field is set to true.canBeUsed
andpriceAdjustment
fields to have a dependencyReference: #17 (comment)
The text was updated successfully, but these errors were encountered: