At Nodes we have been working hard on a Vapor 3 provider for Bugsnag. Bugsnag is a reporting tool that we use extensively to help catch and fix bugs.
In the new version of the library, we've been able to remove a lot of dead code, simplify the API and add support for breadcrumbs.
Migration to Vapor 3
The migration from Vapor 2 to Vapor 3 was a relatively easy one for Bugsnag. The major changes were the use of Codable and the introduction of Futures.
One of the double-edged-swords of Vapor 3 is the asynchronous design. The asynchronous nature of the framework makes stack traces virtually useless. Sadly, we had to remove support for Stack and stack traces.
Registration has seen an update as well. It now uses the Service system.
let reporter =BugsnagReporter(
apiKey: "<YOUR BUGSNAG API KEY>",
shouldReport: environment.name !="local"
With a newly simplified API, we introduced support for severities.
After the migration to Vapor 3, we updated the Bugsnag payload version from 2 to 4. This allows us to support newer features as well as silence warnings about deprecated APIs.
After many feature requests, we have now integrated breadcrumbs into the latest version. Breadcrumb is a feature that helps ease the debugging process by enabling a user to attach data to the life-cycle of a request. To drop a breadcrumb just use the convenience function on Request.
At Monstarlab, we are using SonarQube to gather metrics about the quality of our code. One of the metrics we were interested in is code coverage. However, just running sonar-scanner on the project will not upload the coverage data to our instance of Sonar...
CI Pipelines help improve efficiency by automating complex workflows. With GitHub Actions, it's easier than ever to bring CI/CD directly into your workflow from your repository. Put together with the CI pipeline, a series of automated workflows that help ...