Errbit has supported the Airbrake v3 JSON API since 2015 via:
POST /api/v3/projects/:project_id/create-noticePOST /api/v3/projects/:project_id/notices
The legacy XML v2 endpoint still exists:
GET /notifier_api/v2/noticesPOST /notifier_api/v2/notices
It is parsed through the Hoptoad-named XML code in app/lib/hoptoad.rb and app/lib/hoptoad/v2.rb.
Since v3 JSON support has been available for many years, and hoptoad_notifier is obsolete, should Errbit drop the old XML v2 ingestion path and related tests/fixtures?
Proposed removal scope:
- Remove
/notifier_api/v2/notices
- Remove the Hoptoad XML parser
- Remove XML v2 fixtures/specs
- Keep the v3 JSON API as the supported notice ingestion path
This would be a breaking change for any deployments still using old Airbrake/Hoptoad XML clients, so I wanted to check preference before opening a PR.
Errbit has supported the Airbrake v3 JSON API since 2015 via:
POST /api/v3/projects/:project_id/create-noticePOST /api/v3/projects/:project_id/noticesThe legacy XML v2 endpoint still exists:
GET /notifier_api/v2/noticesPOST /notifier_api/v2/noticesIt is parsed through the Hoptoad-named XML code in
app/lib/hoptoad.rbandapp/lib/hoptoad/v2.rb.Since v3 JSON support has been available for many years, and
hoptoad_notifieris obsolete, should Errbit drop the old XML v2 ingestion path and related tests/fixtures?Proposed removal scope:
/notifier_api/v2/noticesThis would be a breaking change for any deployments still using old Airbrake/Hoptoad XML clients, so I wanted to check preference before opening a PR.