feat: create route handler (POST) for sending user game data

[sheleoni]

Objective:

• Send tideLevel.js object to mongoDB back end

Issue:

• tideLevel is organised in this way:

  const tideLevel =
  {
  // hiragana
  "あ": 5,
  "い": 4,
  "う": 3,
  "え": 2,
  "お": 1,
  "か": 5, ...and so on 

but when we send this object as-is to mongoDB, the object is not recognised and only an _id is added to the document. (ref)

Solution

Settled for now, documented here.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
icecream-sheleoni-com	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 13, 2023 10:57am

[sheleoni]

Problem at: bd141d1

tideLevel is being stored as ObjectId on mongodb, not sure how to go about this.

Tried changing tideLevelSchema to

tideLevel: {
    type: Map,
    of: Number
}

but it did not work.

Also tried using a mixed schema

import mongoose, { Schema, model, models } from "mongoose";

export const userTideLevelSchema = new Schema({
    // kana: String,
    // tideLevel: Number,
        type: mongoose.Schema.Types.Mixed

    },
);

but it did not work.

[sheleoni]

This may be related:

• https://stackoverflow.com/questions/59695467/post-request-is-made-but-only-object-id-is-shown-in-mongodb
• https://stackoverflow.com/questions/66304245/when-i-post-to-mongodb-only-id-is-saved-and
• https://stackoverflow.com/questions/63318541/node-js-post-request-has-data-but-in-mongodb-i-see-only-the-id-not-the-data
• https://stackoverflow.com/questions/24442676/mongoose-schema-types-mixed-not-working

Maybe this will help:

• https://www.mongodb.com/community/forums/t/key-value-pairs-and-how-they-are-listed-in-the-database/161580
• https://www.mongodb.com/blog/post/building-with-patterns-the-attribute-pattern
• https://stackoverflow.com/questions/35422789/how-to-set-up-mongoose-schema-to-store-an-array-of-objects-in-mongodb (mongoDB vs mongoose)
• https://stackoverflow.com/questions/68409017/cannot-save-map-in-mongoose

[sheleoni]

OK it's probably a schema thing, eba40c0 seems to shed us some light! 😢

Achieved (on mongoDB):

By trying out:

        const clonedTideLevel = { kana: "ら", level: 3 };

and

export const userTideLevelSchema = new Schema({
    kana: String,
    level: Number,
    }
);

[sheleoni]

I guess my ultimate question is: store a object with many keys mongoDB or as array?

[sheleoni]

I think we may have to get use to the fact that frontend data structure can be different from backend data structures.

E.g. in the frontend, tideLevel.js:

const tideLevel =
    {
    // hiragana
    "あ": 5,
    "い": 4,
    "う": 3,
    "え": 2,
    "お": 1,
    "か": 5, ...and so on

In the backend: [{ kana: 'あ’, tideLevel: 5, _id: ObjectId('someId') }, { and so on }]

need to see if it's a code problem or not before moving on to this conclusion

[sheleoni]

Settled on this solution for now: b1e18c0 transforms object (e.g. { “あ”: 5, “い”: 2, “う” : 3, “え”: 1 } ) into e.g. [{ “あ”: 5 }, {“う” : 3} ]