Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

metaflow.callflow: should "id" field be the mandatory one? #3503

Merged
merged 1 commit into from Mar 29, 2017
Merged

metaflow.callflow: should "id" field be the mandatory one? #3503

merged 1 commit into from Mar 29, 2017

Conversation

onnet
Copy link
Contributor

@onnet onnet commented Mar 29, 2017

Hi!

Since we've got an option to look for a callflow based on captures, it seems "id" field shouldn't be strictly demanded...
https://github.com/2600hz/kazoo/blob/master/applications/konami/src/module/konami_callflow.erl#L32-L38

Regards,

Hi! 
Since we've got an option to look for a callflow based on captures, it seems "id" field shouldn't be strictly demanded...
https://github.com/2600hz/kazoo/blob/master/applications/konami/src/module/konami_callflow.erl#L32-L38
@lazedo lazedo merged commit bde42c6 into 2600hz:master Mar 29, 2017
lazedo added a commit that referenced this pull request Mar 29, 2017
lazedo added a commit that referenced this pull request Mar 29, 2017
@lazedo
Copy link
Member

lazedo commented Mar 29, 2017

@onnet Thanks! i had to revert because i merged it too soon, sorry. can you please reopen the pull request but also run make apis ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants