Help with setting up content to populate

[listguy]

Does this library still maintained?

[pkosiec]

Yes it is, you can see new commits and releases on the repo. Do you have any issue? If so, please describe it throughtly.

[listguy]

Hey, yes I do have an issue. Just wanted to make sure I'm not putting effort describing the issue for nothing 😅
Anyway I was earlier trying to seed my DB (I am working on mongoDB atlas) with a pre made JSON file. I followed the instructions in importing-data and imported data definition and this is what I came up with:

seeder.js

require("dotenv").config();
const { Seeder } = require("mongo-seeding");
const path = require("path");

const config = {
  database: process.env.MONGO_URI,
  dropDatabase: false,
};

const seeder = new Seeder(config);

const seed = seeder.readCollectionsFromPath(path.resolve("./seeds/tickets"), {
  transformers: [Seeder.Transformers.replaceDocumentIdWithUnderscoreId],
});

seeder
  .import(seed)
  .then((_) => console.log("seeded successfully"))
  .catch((err) => {
    console.log(err);
    console.log("error");
  });

tickets.json:

  [{
    // Array of dummy data objects
  }]

File structure is like so:

     .
   ├── server
   │    ├── seeds
   │    │   └── tickets
   │    │      └── tickets.json
   │    └── seeder.js

When I tried to run seeder.js the code executes and a "seeded successfully" message logged to the console.
However, the collection was still empty. I tried to debug and found out seed was just an empty array [].
Seems like there is a problem in seeder.readCollectionsFromPath()? (No error message was logged to the console)

PS. in the end I managed to dig into the node_modules and follow the errors in the console, and came up with a workaround solution like so:

seeder.js:

require("dotenv").config();
const { Seeder } = require("mongo-seeding");
const fs = require("fs");
const config = {
  database: process.env.MONGO_URI,
  dropDatabase: false,
};

const seeder = new Seeder(config);

// const seed = seeder.readCollectionsFromPath(path.resolve("./seeds/tickets"), {
//   transformers: [Seeder.Transformers.replaceDocumentIdWithUnderscoreId],
// });

const seed = fs.readFileSync("./tickets.json");

seeder
  .import([JSON.parse(seed)])
  .then((_) => console.log("seeded successfully!"))
  .catch((err) => {
    console.log(err);
    console.log("error");
  });

tickets.json:

   {
      "name": "tickets",
      "documents": [
        // mock data ...
      ]
    } 

[pkosiec]

From what I can see you have totally different content from what is described in the documentation here.

You wrote:

seeder.readCollectionsFromPath(path.resolve("./seeds/tickets"), ...)

But in fact you should point to ./seeds:

seeder.readCollectionsFromPath(path.resolve("./seeds"), ...)

Collections are represented by directories. Also, the tickets.json has invalid content. See the document I linked above to fix it.

Closing it for now as it works as described in docs. If it won't work, please write a comment here and I can reopen it 🙂 However, please double check you followed the official guides first. Cheers!

[pkosiec]

I converted the issue to a discussion, as this is proper place for such discussions. In few days I will delete the original issue completely. Of course the whole discussion will be archived here 🙂

[listguy]

Man! I can't believe it was a typo! 😂
I read the documentation closely a few times and still missed the directories path thing. The solution really was just to change "./seeds/tickets" to "./seeds".
It would be nice if there was some kind of a warning for cases like mine (maybe an error to the console). If not, this discussion will do the trick 😄

Works as expected now, thank you for your time and for this awesome library 🙌

[pkosiec]

Glad it worked 👍 However, please keep in mind that the content of your json file is still invalid:

   {
      "name": "tickets",
      "documents": [
        // mock data ...
      ]
    } 

In order to have multiple documents inside the collection, you have to have an array of objects inside JSON:

[{"sampleProperty": "foo"}, {"sampleProperty": "bar"}]

BTW:

It would be nice if there was some kind of a warning for cases like mine (maybe an error to the console). If not, this discussion will do the trick 😄

If you enable debug logging, then you can see which exactly collections are populated. In your case would be no collections at all, so I think it could help a bit.

Cheers!

[listguy]

Yes I know.
This json file is the one I modified to match your structure (as returned from readCollectionsFromPath()) and used it in my workaround.

Thanks again for your patience.

[pkosiec]

Oh, okay. So... enjoy using Mongo Seeding then 🙂 In the meantime you can mark the comment #156 (comment) as answer for your question 🙂 Cheers!