Option to Sync Variant Prices on Multiple Channels about vendure HOT 6 CLOSED

I think this could be handled with a strategy-based approach. This would be the most flexible I think. Something like:

export interface ProductVariantPriceUpdateStrategy extends InjectableStrategy {

  /**
   * This would be invoked whenever a price is changed.
   */
  onPriceUpdate(
    ctx: RequestContect, 
    updatedPrice: ProductVariantPrice, 
    allPrices: ProductVariantPrice[]): Promise<ProductVariantPrice[]> {
    
    // For example, let's get all the other prices with the same currencyCode
    const pricesWithSameCurrency = allPrices.filter(p => p.currencyCode === updatedPrice.currencyCode);
   
    // we can now sync the prices
    pricesWithSameCurrency.forEach(p => p.price = updatedPrice.price);
 
    // any returned ProductVariantPrice entities will have the new price
    // persisted to the DB.
    return pricesWithSameCurrency;
  }

}

I quite like this approach because:

* It requires zero changes to the data model

* It can handle different sync directions. E.g. one-way sync only from default channel to child channels, or two-way sync as in this example.

* It can be used for other use cases. For instance, let's say you wanted to have automatic currency conversion. This mechanism could be used to do a lookup on exchange rates and update other currencies accordingly.

Very nice approach! This way will be much better

from vendure.

I think this could be handled with a strategy-based approach. This would be the most flexible I think. Something like:

export interface ProductVariantPriceUpdateStrategy extends InjectableStrategy {

  /**
   * This would be invoked whenever a price is changed.
   */
  onPriceUpdate(
    ctx: RequestContect, 
    updatedPrice: ProductVariantPrice, 
    allPrices: ProductVariantPrice[]): Promise<ProductVariantPrice[]> {
    
    // For example, let's get all the other prices with the same currencyCode
    const pricesWithSameCurrency = allPrices.filter(p => p.currencyCode === updatedPrice.currencyCode);
   
    // we can now sync the prices
    pricesWithSameCurrency.forEach(p => p.price = updatedPrice.price);
 
    // any returned ProductVariantPrice entities will have the new price
    // persisted to the DB.
    return pricesWithSameCurrency;
  }

}

I quite like this approach because:

• It requires zero changes to the data model
• It can handle different sync directions. E.g. one-way sync only from default channel to child channels, or two-way sync as in this example.
• It can be used for other use cases. For instance, let's say you wanted to have automatic currency conversion. This mechanism could be used to do a lookup on exchange rates and update other currencies accordingly.

from vendure.

@NoahPerez It's not available yet - it is going to be released in v2.2. You can try it now by installing the pre-release v2.2.0-next.3

from vendure.

Within the next 2-3 weeks is very likely.

from vendure.

@dylviz Where should I add ProductVariantPriceUpdateStrategy strategy-based approach or export it as a plugin?

or should I wait for Vendure 2.2 ?

from vendure.

@michaelbromley okay thanks, I will install the pre-release "@vendure/core": "2.2.0"
Do you know when you will release V2.2 ? i saw some nice improvements

from vendure.