You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue ported from old casework github repo (issue 15). Original author: casework
Why is there a separate isRead for SMSMessage? A regular message like "WhatsApp" could also have this field.
Response by sbarnum:
I don't know if there is any specific reason for it to be in SMSMessage specifically rather than in Message.
I believe it originally came from mapping the Hansken model in and Hansken has 'read' as a property of textMessage.
I would agree that it seems like it would be appropriate to move to Message.
If nobody disagrees we can add an issue to the UCO tracker proposing moving isRead from SMSMessage to Message property bundle and then deleting the SMSMessage property bundle since isRead is its only current property.
Response by casework:
Agreed.
The text was updated successfully, but these errors were encountered:
Issue ported from old casework github repo (issue 15).
Original author: casework
Why is there a separate
isRead
forSMSMessage
? A regular message like "WhatsApp" could also have this field.Response by
sbarnum
:I don't know if there is any specific reason for it to be in SMSMessage specifically rather than in Message.
I believe it originally came from mapping the Hansken model in and Hansken has 'read' as a property of textMessage.
I would agree that it seems like it would be appropriate to move to Message.
If nobody disagrees we can add an issue to the UCO tracker proposing moving isRead from SMSMessage to Message property bundle and then deleting the SMSMessage property bundle since isRead is its only current property.
Response by
casework
:Agreed.
The text was updated successfully, but these errors were encountered: