Cosmos Stored Procedure - console.log issue

Question

I'm new to Cosmos DB stored procedure. As introduced, cosmos stored procedure is written with Javascript, and it's unable to debug by setting up the break point, so we'll have to use console.log(...) to watch element content inside the stored procedure. Here is one of my example, which is to retrieve an item from my collection based on the input parameter prefix (the 'id' property in my item), and using javascript-query-api

function example(prefix) {
    //not working with ','
    //console.log('input prefix: ', prefix);
    //this works with '+'
    console.log('input prefix: ' + prefix);
    var collection = getContext().getCollection();
    //cannot view what's collection represents
    console.log('collection:' + JSON.stringify(collection));
    collection.chain().filter(function (doc) {
        //un-comment below will make the console log blank...
        //console.log('inside filter prefix: ' + prefix);
        return doc.id == prefix;
    }).map(function (doc) {
        return {
            id: doc.id,
            price: doc.price
        }
    }).value();
}

Here is my console.log window

My console.log won't do a line break or working with comma ',':

So a summary of couple of issues I had are:

• console.log inside the stored procedure won't work with comma - , but only works with colon - :
• console.log won't do a line break... even I add \n inside...
• I cannot get what's really inside the collection object even I've deserialized it, as you can see from screenshot it's shown as {\"spatial\":{}}
• If I wanted to look into what the input parameter - prefix passing inside my filter function, when I un-comment my console.log('inside filter prefix: ' + prefix);, then my console log screen will show only an empty string somehow which is really ...
• Adding more details for data schema, partition key and stored procedure execution detail

Data schema:

Stored procedure execution detail:

Stored procedure result and console.log:

Answer 1

1. console.log inside the stored procedure won't work with comma - , but only works with colon - :

Yes,actually it only does works with +,so please use + to combine the log information.

2. console.log won't do a line break...even I add \n inside...

If you observe the output of log in the portal console, entire log info is shown as a long string. So, even though you add \n, it was identified as a part of string. You could add some special character like *** or ----- to distinguish.

3. I cannot get what's really inside the collection object even I've deserialized it, as you can see from screenshot it's shown as {\"spatial\":{}}

Since SP is run on the server side,i believe that we can't access every object as locally sdk. Based on the statements listed here:

Stored procedures and triggers are registered for a particular collection. The collection object supports create, read, update and delete (CRUD) and query operations on documents and attachments in the current collection.

We could think more of collection as a base object for calling CRUD methods.Like a init client in the sdk which is used to invoking methods.

4. If I wanted to look into what the input parameter - prefix passing inside my filter function, when I un-comment my console.log('inside filter prefix: ' + prefix);, then my console log screen will show only an empty string somehow which is really ...

Test your code,the inside prefix log does works.