mysportsfeeds / mysportsfeeds-node Goto Github PK

if the underlying http call to msf.getData returns a 204, that seems like a place where we'd like to reject the promise so we can handle it in a catch rather than doing a null check ?

I'm performing the following API call using the Node.js package:

var msf = new MySportsFeeds("1.2", true, null);
var today = new Date();

var data = msf.getData('nhl', '2017-2018-regular', 'scoreboard', 'json', { 
	fordate: today.getFullYear() + 
		('0' + parseInt(today.getMonth() + 1)).slice(-2) + 
		('0' + today.getDate()).slice(-2),
	force: true
});

console.log(data);

The results in data is { state: 'pending' }. I've removed the authenticate call from the example. When I don't specify null for the store to file, the data is saved successfully on disk.

Am I doing something wrong?

On line 66 of API_v1_0.js, fs.mkdir() is used without providing a call back function, causing the save to crash. Changing this to fs.mkdirSync() solves the problem.

Hey! This is very useful for a small project that I've been working on, but I'm trying to change the storeLocation. What's the best way to do this?

Is there a way to work with scrambled API??