This crate should be used as a build dependency in Rust consumers.
In their `build.rs` they can call the builder to auto-generate code from
`metrics.yaml` and `pings.yaml` definitions:
glean_build::Builder::default()
.metrics("metrics.yaml")
.pings("pings.yaml")
.generate()
.expect("Error generating Glean Rust bindings");
This requires a working Python3 & pip installation.
Windows untested.
Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1713573 and https://bugzilla.mozilla.org/show_bug.cgi?id=1772566
This creates a new crate `glean-uniffi` that will be consumed by the
different foreign-language SDKs.
Eventually `glean-core` and `glean` should go away and be merged into
that `glean-uniffi`
When locally building or installing glean this file is generated.
It trips up flake8, because it definitely does not correspond to its
standards.
It's auto-generated, so there's no need for linting,
let's just ignore it.
This adds the custom URL handling to provide the Glean debug functionality. This also adds the functionality to the glean-sample-app and the documentation on how to add and use this in a consuming application.
* Implement counter metric type for Python bindings.
It's pretty helpful to have type annotations for the documentation, if nothing
else, so additionally, this adds support for mypy type annotations.
* Simplify CircleCI task name
* Add a bug number
When tests are run this file gets copied to 'Cartfile'
Having a Cartfile and pulling this project from another project using carthage, will
cause any Cartfile here to be run, and there is currently a carthage bug
whereby pulling OHHTTPStubs reports a circular dependancy error (incorrectly).