Allow hooks to use options in context

Here you go - a nice & simple patch :) The context array will be available in hooks via $entity->context, and will get otherwise ignored whilst saving a log entity.

In this case, service decorator is a better option; http_client_log.services.yml is an example.

I'm well aware that service decorators could be ideal (and I have implemented many before elsewhere); but I don't see how that would help here? I'm looking for a way to get something from the options array, into the log entity. The log entity is created inside \Drupal\http_client_log\Logger\Logger::log(), and as far I can see, that whole method would need replacing in order to do this, so decoration couldn't really help, unless that class was first rearchitected to introduce an opportunity in between the entity being created and saved?

If decoration, or replacing the service class was used, there's not much from this module that's actually left in use, beyond the entity type definition. Which seems a shame! My suggestion to include the context in the log entity is simply to make the data available so that there is an opportunity for extensibility.

Or can you help me see how decoration could actually be used to take input from the options array, to set field values on the log entity, given the current module code?

Hi James, commited.

Thanks very much!

Automatically closed - issue fixed for 2 weeks with no activity.