Support Extended JSON format

Hi @pkosiec,

Awesome job at the library, it’s very useful.

I’m running into an issue. I’m inserting data from a JSON file. In the file I have an “_id” field which should be MongoDB ObjectId.

The issue is that it gets inserted as plain text.

This syntax should lead to the creation of ObjectIds:

{ 
 "_id" : {"$oid":"5a68fdc3615eda645bc6bdec"}
}

But it throws an error locally: { MongoSeedingError: Error: key $oid must not start with '$'

I found that syntax here: https://stackoverflow.com/questions/51439955/mongoimport-id-is-not-an-objectid

Is there a way to end up with ObjectIds instead of plain text ids?

Thank you

[pkosiec]

Hi @Fiyin-Anne, Because EJSON parsing is enabled by default for all JSON files, it should work normally. Just to double check: do you have something like this in your json file?

{ 
 "_id" : {"$oid":"5a68fdc3615eda645bc6bdec"}
}

If so, it should work.

The error you provided shouldn’t be related to the EJSON parsing mode. Anyway, currently there is no support for changing mode of EJSON parsing, however I will introduce it very shortly.

[pkosiec]

Hi @mtapdilli, I’m using EJSON parser from official MongoDB bson package. What I do is

return EJSON.parse(content, {
   relaxed: true,
});

https://github.com/pkosiec/mongo-seeding/blob/master/core/src/populator/filesystem.ts#L125

However, maybe the relaxed mode messes things up?

Relaxed Mode A string format that emphasizes readability and interoperability at the expense of type preservation. That is, conversion from relaxed format to BSON can lose type information.

Could you please try using canonical mode e.g. with modified mongo-seeding that uses this mode while parsing EJSON? If that will be the case, I can add additional parameters to configure EJSON parsing mode.

Cheers!