Skip to content
This repository has been archived by the owner on Aug 5, 2024. It is now read-only.

nexmo cc cli issue #198

Open
Namr-ta opened this issue Feb 27, 2019 · 1 comment
Open

nexmo cc cli issue #198

Namr-ta opened this issue Feb 27, 2019 · 1 comment
Labels

Comments

@Namr-ta
Copy link

Namr-ta commented Feb 27, 2019

Steps to reproduce

Tell us what you did
When i use CLI to create a conversation:

Expected behavior

Tell us what should happen

nexmo cc name="bridge" display_name="bridge_name"
{uuid: "CON-75b81752-4512-4798-9dcd-c72a57c8c075", name: "bridge", display_name: "bridge_name", timestamp: {…}, sequence_number: 0, …}

Actual behavior

Tell us what happens instead

The conversation has property reversed refer below name and display_name has swapped
{uuid: "CON-75b81752-4512-4798-9dcd-c72a57c8c075", name: "bridge_name", display_name: "bridge", timestamp: {…}, sequence_number: 0, …}

System configuration

Node version:

NPM version:

Operating system:

@AlexLakatos AlexLakatos added the bug label May 1, 2019
@Chael1216-Hash
Copy link

Jhon Michael alburo Tababa

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants