discourse/lib/service
Loïc Guitaut f79dd5c8b5 DEV: Stop injecting a service result object in the caller object
Currently, when calling a service with its block form, a `#result`
method is automatically created on the caller object. Even if it never
clashed so far, this could happen.

This patch removes that method, and instead use a more classical way of
doing things: the result object is now provided as an argument to the
main block. This means if we need to access the result object in an
outcome block, it will be done like this from now on:
```ruby
MyService.call(params) do |result|
  on_success do
    # do something with the result object
    do_something(result)
  end
end
```

In the same vein, this patch introduces the ability to match keys from
the result object in the outcome blocks, like we already do with step
definitions in a service. For example:
```ruby
on_success do |model:, contract:|
  do_something(model, contract)
end
```
Instead of
```ruby
on_success do
  do_something(result.model, result.contract)
end
```
2024-10-22 16:58:54 +02:00
..
action_base.rb DEV: Introduce a Service::ActionBase class for service actions 2024-09-18 17:02:46 +02:00
base.rb DEV: Drop OpenStruct for the context object in services 2024-10-08 10:34:55 +02:00
contract_base.rb DEV: Have contract take a block in services 2024-10-02 17:00:01 +09:00
policy_base.rb DEV: Introduce a Service::ActionBase class for service actions 2024-09-18 17:02:46 +02:00
runner.rb DEV: Stop injecting a service result object in the caller object 2024-10-22 16:58:54 +02:00
steps_inspector.rb DEV: Drop OpenStruct for the context object in services 2024-10-08 10:34:55 +02:00