As a library author and application developer, I'd find this much simpler to use if I'm only working with one library since I expect this functionality to be present.
Very open-minded to improvements or suggested tweaks, however!
Checklist
[x] The provided tests still run.
[x] I've created new tests where needed.
[x] I've updated the documentation if necessary.
Motivation and Context
We want to provide a simple solution for end-users to take advantage of. swift-metrics has broad applicability across the community, and is already included in the dependency graph. If a user does not wish to use swift-metrics they don't need to, but this change will make it much clearer how to do so.
This fixes #5.
Description
I moved PrometheusMetrics into the Prometheus target, which composes SwiftPrometheus.
In addition, I created a PrometheusExample executable to make it easier for users to see the output format and follow along with the code (particularly from within Xcode 🔨 ).
MrLotU
commented
5 years ago
This is following discussion in #5.
As a library author and application developer, I'd find this much simpler to use if I'm only working with one library since I expect this functionality to be present.
Very open-minded to improvements or suggested tweaks, however!
Checklist
Motivation and Context
We want to provide a simple solution for end-users to take advantage of.
swift-metricshas broad applicability across the community, and is already included in the dependency graph. If a user does not wish to useswift-metricsthey don't need to, but this change will make it much clearer how to do so.This fixes #5.
Description
I moved
PrometheusMetricsinto thePrometheustarget, which composesSwiftPrometheus.In addition, I created a
PrometheusExampleexecutable to make it easier for users to see the output format and follow along with the code (particularly from within Xcode 🔨 ).