Closed (won't fix)
Project:
Commerce Core
Version:
8.x-2.x-dev
Component:
Product
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
11 Jan 2018 at 14:58 UTC
Updated:
10 Feb 2018 at 22:21 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
sorabh.v6Comment #3
gauravjeet commentedfield_costis a generic name and might be in use on sites. Anything new to this field might break existing functionality for cost. I suggest the field be name something that relates to the module from which it originates, something likefield_commerce_cost, orcommerce_costComment #4
Anonymous (not verified) commentedWhat about commerce_purchasing_price? This has a clear meaning and reflects the use case for this field. Generally is this field a good idea.
Comment #5
bojanz commentedThe name should be just "cost". We don't prefix base fields nor fields added via traits.
Comment #6
sorabh.v6@bojanz Okay, I'll change the name from field_cost to cost.
Thanks for the feedback.
Comment #7
sorabh.v6Comment #8
sorabh.v6Field cost changed to cost. Please review.
Comment #9
travis-bradbury commentedI've played around with this here: https://www.drupal.org/project/commerce_cost
I want cost on order items too, since I want to know the profit of an item when it was sold, not profit based on whatever the current costs are.
The module currently does:
and a couple extras:
I think we can move the whole first list into core here if it's considered useful (or at least not harmful).
Comment #10
bojanz commentedSounds like you have a decent contrib plan, making it unnecessary to partially solve the problem in Commerce itself.