Hey Andrei,

How big of a pain would it be to add another ShoppingCartType to the enum, specifically the following.


namespace Nop.Core.Domain.Orders
{
    /// <summary>
    /// Represents a shopping cart type
    /// </summary>
    public enum ShoppingCartType
    {
        /// <summary>
        /// Shopping cart
        /// </summary>
        ShoppingCart = 1,
        /// <summary>
        /// Wishlist
        /// </summary>
        Wishlist = 2,
        /// <summary>
        /// Draft
        /// </summary>
        Draft = 3,
    }
}


I use nop for a web-2-print solution and having that draft option allows me to add something to the cart but not show it until the user goes through the draft workflow (in our case building imprint and production art for the item). Currently it is the only file in Nop.Core I cannot extend but have to fix every time I update from source.