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

Incoming number sent to JS listener #2

Open
beradrian opened this issue Mar 23, 2015 · 6 comments
Open

Incoming number sent to JS listener #2

beradrian opened this issue Mar 23, 2015 · 6 comments

Comments

@beradrian
Copy link

It would be useful if instead of the state as a string on the JS listener you'll receive an object with two properties: state and incomingNumber.

@leonzinger
Copy link

+1
And caller name if in phone book :)

@renanoliveira
Copy link
Owner

Hi @beradrian and @leonzinger

Today I have two pull requests about this.
I need study this solution because one used a json object ({"RINGING": "NUMBER}) for all states and other concatenate number on ringing state (RINGING + "NUMBER").

Do you have any preference?

@guillaume-fr
Copy link

It's better to have a JSONObject with the following definition : { state:"RINGING", number:"NUMBER}

It's explicit and avoids breaking changes if you want to add caller name or any other info later.

@leonzinger
Copy link

I prefer JSON as well.

Thank you!

On Mon, Oct 26, 2015 at 11:50 AM guillaume-fr [email protected]
wrote:

It's better to have a JSONObject with the following definition : {
state:"RINGING", number:"NUMBER}

It's explicit and avoids breaking changes if you want to add caller name
or any other info later.


Reply to this email directly or view it on GitHub
#2 (comment)
.

@beradrian
Copy link
Author

I agree with @guillaume-fr { state:"RINGING", number:"NUMBER}. JSON is much better.

@RishabhKothaari
Copy link

Hi @renanoliveira thanks for the plugin , can you pull this fix #7 .

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

No branches or pull requests

5 participants