Skip to content

VAPI-3162: Add ReferCompleteCallback and ReferCallStatusEnum (fixes spec parse error in #211)#212

Closed
Copilot wants to merge 1 commit into
VAPI-3162from
copilot/vapi-3162-regenerate-refer-sdk-files
Closed

VAPI-3162: Add ReferCompleteCallback and ReferCallStatusEnum (fixes spec parse error in #211)#212
Copilot wants to merge 1 commit into
VAPI-3162from
copilot/vapi-3162-regenerate-refer-sdk-files

Conversation

Copilot AI commented Jun 19, 2026

Copy link
Copy Markdown

Summary

Fixes the CI failures seen in PR #211 (VAPI-3162-REFER).

Root cause: spec/unit/models/refer_complete_callback_spec.rb in PR #211 accidentally contains a spurious first line — a GitHub diff-table header (Original file line number\tDiff line number\tDiff line change) — that was pasted in when the file was authored. Ruby cannot parse it, causing:

NameError: undefined local variable or method `change' for main:Object
# ./spec/unit/models/refer_complete_callback_spec.rb:1:in `<top (required)>'

Changes

  • bandwidth.yml — adds referCallStatusEnum and referCompleteCallback schemas
  • lib/bandwidth-sdk/models/refer_call_status_enum.rb — new enum model
  • lib/bandwidth-sdk/models/refer_complete_callback.rb — new callback model
  • lib/bandwidth-sdk.rb — registers both new models
  • .openapi-generator/FILES — registers both new files
  • spec/unit/models/refer_call_status_enum_spec.rb — unit tests for the enum
  • spec/unit/models/refer_complete_callback_spec.rb — unit tests for the callback (without the bad header line)

- Add referCallStatusEnum schema to bandwidth.yml
- Add referCompleteCallback schema to bandwidth.yml with standard call
  context fields plus refer-specific fields (referTo, referCallStatus,
  referSipResponseCode, notifySipResponseCode)
- Copy OpenAPI-generator-produced model files:
  lib/bandwidth-sdk/models/refer_call_status_enum.rb
  lib/bandwidth-sdk/models/refer_complete_callback.rb
- Register both models in lib/bandwidth-sdk.rb and .openapi-generator/FILES
- Add unit tests covering success, failure (405 rejected), and failure
  (202 + notifySipResponseCode) scenarios
@bwappsec

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@atelegu atelegu closed this Jun 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants