Linted some parts of code

[nikhilponnuru]

used global directives to avoid warnings and errors shown by jshint and jslint
changed way of accessing object properties
used concept of javascript hoisting and declared variable -'messaging' before it is used [as it is the recommended practice ]

[irdan]

You will want to target the develop branch for most PR's. Some of these issues may have already been addressed there.

[nikhilponnuru]

@irdan but these are being mentioned in code climate which is suggested by privly in documentation to follow for bug tracing
[ this I am saying because I thought code climate will be reflected with changes in code when merged ...am I wrong with this assumption ? ]

[smcgregor]

Development targets the develop branch. CodeClimate doesn't let me change the default branch, for some reason.

[nikhilponnuru]

@smcgregor hey should I focus on develop branch to contribute to this project and my pull request can't it be accepted ?

[smcgregor]

Yes, all contributions should be made against the develop branch of the repository. If you are submitting this pull request with the purpose of completing the "levels" on our development guide, you can consider L0 to be completed. I won't be merging this pull request since the files have since changed.

[smcgregor]

@nikhilponnuru If you want this PR to be accepted, you should close it and open a new one against the develop branch. Thanks!