jprichardson / jprichardson/node-google
Undefined Links?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 456
- Forks
- 115
- PR merge metrics
- No merged PRs in 30d
Description
Can't figure out why I'm only getting undefined results when running the test?
Not even getting an error, just nothing.
This is what i ran --
var google = require( "./google/lib/google.js" );
google.resultsPerPage = 25;
var nextCounter = 0;
google( 'node.js best practices' , function( err , next , links )
{
if( err )
{
console.error( err );
}
console.log( links.length );
for( var i = 0 ; i < links.length ; i++ )
{
console.log( links[i].title + ' - ' + links[i].link );
console.log( links[i].description + "\n" );
}
if( nextCounter < 4 )
{
nextCounter+=1;
if( next )
{
next();
}
}
});
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported command against google/lib/google.js and inspect how the callback receives links and their title, link, and description fields. Determine why the example produces undefined results, then verify the behavior with the project's available test command or a focused regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, search
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100