Correctly using JavaScript API authorization credentials with twitter_config

[dsx]

I’m using JavaScript to connect with the Twitter API, per the instructions on this Github

BoyCook/TwitterJSClient

And I’m using the recommended update using twitter_config and Twitter.js for authorization.

My question regards the handling of the Twitter authorization credentials on the index.js file, below:

//Get this data from your twitter apps dashboard

var config = {

{

"consumerKey": "XXX";,

"onsumerSecret": "XXX",

"accessToken": "XXX",

"accessTokenSecret": "XXX",

"allBackUrl": "XXX";

}

// make a directory in the root folder of your project called data

// copy the node_modules/twitter-node-client/twitter_config file over into data/twitter_config` DS: twitter_config isn't in twitter-node-client.

// Open `data/twitter_config` and supply your applications `consumerKey`, 'consumerSecret', 'accessToken', 'accessTokenSecret', 'callBackUrl' to the appropriate fields in your data/twitter_config file

var twitter = new Twitter();

I’m assuming the XXXs above indicate places to insert the Twitter authorization credentials?

If I understand the point of using the twitter_config file to hold the authorization credentials, it keeps the credentials out of the index.js file. (though admittedly I don’t know why that’s a positive).

So I’m trying to confirm if I do insert the Twitter authorization credentials into XXX for the Twitter API call above, which is in the index.js file.

And if so, can you tell me the point of using twitter_config if the credentials still go into the index.js file? The original version of the code above doesn’t have the “var config” in the Twitter authorization.

Thanks

[dsx]

As an update, in the above config variable, i entered “” for “XXX”.

When I tried to deploy the function, I received the following error message:

ERROR MSSG

Deployment failure:
Function load error: Code in file index.js can't be loaded.
Is there a syntax error in your code?
Detailed stack trace: /srv/index.js:56
twitter.getSearch({'q':' #voicefirst', since:’2018-10-18 15:24:15', ‘user’, ‘text’, ‘retweet_count’, 'result_type':'popular'}, error, success);
                                             ^

SyntaxError: Invalid or unexpected token
    at createScript (vm.js:80:10)
    at Object.runInThisContext (vm.js:139:10)
    at Module._compile (module.js:616:28)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3)
    at Module.require (module.js:596:17)
    at require (internal/module.js:11:18)
    at getUserFunction (/worker/worker.js:391:24)

It identifies the Search Query as a potential problem, but not the authorization. Does that mean the authorization is ok? Because I entered “” in place of the “XXX” in the authorization credentials in the index.js file:

SEARCH QUERY
twitter.getSearch({‘q’:’ #voicefirst’, since:’2018-10-18 15:24:15’, ‘user’, ‘text’, ‘retweet_count’, ‘result_type’:‘popular’}, error, success);

I’ve stitched this code together from various sources, so if anyone has any direction on how to troubleshoot what’s going on, greatly appreciated.

[andypiper]

To answer the first question - the usual reason for putting tokens into a separate file would be to keep them private just to your deployment of the app, and not committed to source control, for example. However, a better approach would be to load them from environment variables, so that they can’t easily be leaked in the code itself.

The second issue you’re asking about appears to be that the query you’re passing in is using smart quotes ’ instead of plain quotes ' in several places in the query string.

[system]

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.