Comments refactor about refresh HOT 1 CLOSED

So, there's two ways I can see this going. Both are a little bit annoying to deal with.

The first is decently similar to what we currently do in Realm (as in, data is stored under one type). We have one table full of all comments, with the model having something like this:

public class GameComment
{
    public int? LevelId { get; set; }
    public ObjectId? ProfileId { get; set; }
    public int? PhotoId { get; set; } // (in the future)

    // ...
}

I like this, but it comes with the advantage of bloating up the model a bit, and it becomes a bit janky in regards to retrieving the host object and serializing it. We already have a system like this for Events, and to be frank it's a bit of a pain to deal with both internally and in refresh-web.

The other approach to use is having multiple tables. So, instead of storing multiple host object keys in the first approach, we have a dedicated table & class for each time a comment can be posted to an object:

public interface IComment
{
    // ...
}

public class ProfileComment : IComment
{
    public GameUser? Profile { get; set; }
}

public class LevelComment : IComment
{
    public GameLevel? Level { get; set; }
}

public class PhotoComment : IComment
{
    public GamePhoto? Photo { get; set; }
}

Maybe we could have it be IComment<THost> or something to keep API response types or w/e simple, but that's the idea. This comes at the cost of having to juggle multiple tables but I think that's better than juggling different keys on one table.

I lean towards the second approach, personally.

from refresh.