LuanandGitHub ea53aa9362 Migrate usage of metrics.Handler to metricDefinition.With (#5435) ...

## What changed?
Using the new metricDefinition.With approach.

## Why?
The usage of metrics.Handler could be both redundant and unsafe:

```
 handler.Histogram( myHisto.Name(), myHisto.Unit() ).Record(...)
                │             │               └───┐
                │             │                   │
                └─────┐       └───────────┐       │
                      │                   │       │
       Redundant and Unsafe: 'Histogram'  │       │
       is specified despite knowing       │       │
       'myHisto' is a histogram. There's  │       │
       also a risk if 'myHisto.Name()'    │       │
       refers to a metric definition that │       │
       is not a histogram.                │       │
                                          └─── Redundant information
```

And using the new With(Handler) method, there's no need to specify
redundant information.


## How did you test it?
Already exists an ExampleHandler which tests all the new approach
methods.

## Potential risks
People can still use the old approach, because we are keeping
the Handler interface as-is.

## Is hotfix candidate?
No.

2024-03-07 23:09:49 +00:00

..

activities_test.go

Replace gogo/protobuf with google/protobuf (#5032)

2023-11-21 15:19:37 -08:00

activities.go

Migrate usage of metrics.Handler to metricDefinition.With (#5435)

2024-03-07 23:09:49 +00:00

force_replication_workflow_test.go

Replace gogo/protobuf with google/protobuf (#5032)

2023-11-21 15:19:37 -08:00

force_replication_workflow.go

Replace gogo/protobuf with google/protobuf (#5032)

2023-11-21 15:19:37 -08:00

fx.go

Register system workflow activities with default worker (#5017)

2023-10-23 16:42:08 -07:00

handover_workflow_test.go

Misc changes to migration workflow (#2838)

2022-05-12 10:23:19 -07:00

handover_workflow.go

Allow specifying a dedicated activity worker for system worker components (#4854)

2023-10-16 11:57:51 -07:00