UserModel : This is complete. There is no need to store listings in the user model, rather mantain a object ref in the listings and pools itself for easy access and filtering (read only optimized)
PoolModel : This is also basically done.
ListingsModel : This is the trickiest one for 2 reasons:
For images, storing buffers (actual binary image data) isnt efficient, so currently ive configured it to store images as urls to the images. We need to integrate a file system like Amazon s3 to store images of a listing when it comes in see #36.
Since we have different investment types, some of the finer details (sqft, franchise name, bedrooms etc.) will be in one type but not another. Having every single field and setting it to optional is a code smell and not a good way of doing things. So currently I have set details to take in just an object of data, with no schema defined for it. Might need to change this later.
UserModel : This is complete. There is no need to store listings in the user model, rather mantain a object ref in the listings and pools itself for easy access and filtering (read only optimized)
PoolModel : This is also basically done.
ListingsModel : This is the trickiest one for 2 reasons:
closes #10 #9 #8