Support simple API names and add `locale` property

[yoichiro]

This pull request will fix #8.

What is this pull request

In this current version, the names of APIs tend to be verbose. Especially, they are the followings:

• startConversation(), startConversationWith()
• endConversation()
• setLocale()

In this pull request, these aliases are provided. That is, the following APIs are provided:

• start(), startWith()
• cancel()
• locale (used as action.locale = 'ja-JP')

How to implement them

For adding the locale property, I will add a new definition of the locale setter method into the ActionsOnGoogle class.

For adding the alias methods, I will add the alias method definitions to the prototype of the ActionsOnGoogle class.

[yoichiro]

@Canain I have changed the alias approach to adding methods simply. I would like you to check the following:

• start() alias method: https://github.com/actions-on-google/actions-on-google-testing-nodejs/pull/11/files#diff-59d7d620304bea33809f81e10d79406eR287
• startWith() alias method: https://github.com/actions-on-google/actions-on-google-testing-nodejs/pull/11/files#diff-59d7d620304bea33809f81e10d79406eR298
• cancel() alias method: https://github.com/actions-on-google/actions-on-google-testing-nodejs/pull/11/files#diff-59d7d620304bea33809f81e10d79406eR306

[Canain]

@Fleker can you take a look and see if it works for you?

[Fleker]

I do like the more concise methods, although I am hesitant to start creating a bunch of aliases for methods before we even get to a v1 as it'll end up cluttering the API.

Maybe we should use these new methods as the default way and deprecate the current versions. We can accept the aliasing for now, with a plan to remove those verbose method names in a v1 release.

[yoichiro]

@Fleker @Canain Thank you for the confirmation. Ok, I intend to change my code to the following:

• Move the implementation code to each new method. And, change the code of each original method to call the corresponding new method.
• Introduce a typedoc. And, put the @deprecated annotation on the original methods to represent that the original methods will be removed.

I would like you to review again after I change and commit them.

[yoichiro]

@Fleker @Canain Could you review the following commits?

• dbe1a9d - Move the implementation code to each new method. And, change the code of each original method to call the corresponding new method.
• 946b4bd - Introduce a typedoc. And, put the @deprecated annotation on the original methods to represent that the original methods will be removed.

[yoichiro]

@Fleker I have just changed codes you mentioned. Could you review diffs 3086897 5d3dbd4 1336a5e again? BTW, I removed method names which are deprecated from the README.md at 1336a5e to navigate to use the new simple methods.

[Fleker]

@atulep what do you think? It looks fine to me.

[yoichiro]

@atulep Could you confirm this?

[yoichiro]

@atulep Thank you for the reviewing. Both answers of the questions are yes. I do them.

[yoichiro]

@atulep Could you review their changes below?

• Can you also change examples/facts-about-google-ts to use simplified interface, since you modified both of the other examples? -> b12972c
• Can you change the src/test/ to use updated API? -> e2d617d

[yoichiro]

@atulep Thank you for the reviewing!

[yoichiro]

@Fleker @Canain Could you do this final judgement?

[Fleker]

Yeah this looks good to me.

[Canain]

Looks good to me.

[yoichiro]

@Canain @Fleker @atulep Thanks, guys. Can somebody merge this to the master branch? :)

[Fleker]

I ran the tests and everything is good. We'll do the merge and release on Monday, so as not to break things over the weekend. :grin:

[yoichiro]

@Fleker Ok, have an enjoy your weekend!