Open zdrossman opened 9 years ago
This is not a blocker. I can sub in a method that fakes it until you have time @nayan-leo.
We should discuss this one. Ids for patient and users may collide, so as we have done in the past we may need to set up compound/complex keys
I have been petitioning for the change to string-based (complex) ids since I joined Leo! :) But I don't think we need them for this specific reason, since we aren't planning on accounting for patients having access to the app anytime in the near future. Definitely a good idea regardless.
Problem: Not only do we think this would be much more efficient, but
JSQMessagesViewController
expects it.Solution: Remove rest of user object and replace with simple
_id
field for each user associated with the object (e.g. booked_by_user_id, sender_id, escalated_to_id, escalated_by_id, etc.)