commerce.availability_manager needs to pass what "phase" we're checking in

drugan proposed one way is to pass the current class in \Drupal\commerce\Context. We can pass an arbitrary data array, one of which can be the current step.

His proposal followed this:

+    $context = new Context($order->getCustomer(), $order->getStore(), time(), [
+      'caller' => self::class,
+    ]);

This turns into more of a pattern than something we can concretely set. The class name doesn't fit current patterns, but this is actually how the event dispatcher works in Symfony 5. The dispatcher uses the class name as the event name unless a specific event name is provided. However, this isn't sustainable if someone made a custom add to cart form (class wouldn't match.) The availability manager also doesn't know about carts, orders, or checkout. Those concepts are provided by the components in Commerce.

@drugan sorry, step here means more of what phase verus quantity number steps. Retitling. This way the availability manager could say if it was Add to cart, Entering Checkout, Placing an order.

Often times we have a database cache layer in Drupal for stock levels. But when entering checkout there is a hard ping to the remote ERP to check live inventory levels.

Actually, this issue was created before the availability manager check received a context object: #2803221: Create context value object for price resolvers and availability checkers.

I think we can close this issue as there isn't anything else to really do. Custom implementations could pass a step. Or we could opt to modify the order refresh code to provide context data.

  public function process(OrderInterface $order) {
    // @todo Get $context as an argument to process().
    $context = new Context($order->getCustomer(), $order->getStore(), NULL, [
      'phase' => 'refresh',
    ]);

I'm going to just close this issue. Providing a context object "fixed" this issue. Instead of adding a phase parameter it could be part of the context object.