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
When introducing the message entity in #1, we considered the possibility of a message thread entity relationship. Somehow I didn't end up discussing it at all in the ticket though. I'm not sure if it would really be useful or not, but I wanted to note that I'd created this class for it, if we ever revisit this:
<?php/** * Message thread entity relationship class. * * @package WordPoints_BuddyPress * @since 1.0.0 *//** * Defines the relationship between a message and the thread it is a part of. * * @since 1.0.0 */class WordPoints_BP_Entity_Message_Thread
extends WordPoints_Entity_Relationship_Stored_Field {
/** * @since 1.0.0 */protected$storage_type = 'db';
/** * @since 1.0.0 */protected$primary_entity_slug = 'bp_message';
/** * @since 1.0.0 */protected$related_entity_slug = 'bp_message_thread';
/** * @since 1.0.0 */protected$related_ids_field = 'thread_id';
/** * @since 1.0.0 */publicfunctionget_title() {
return__( 'Thread', 'wordpoints-bp' );
}
}
// EOF
The text was updated successfully, but these errors were encountered:
I think possibly that the decision had to do with the fact that we don't support array targets. But I'm not 100% sure. We may have just concluded that it wasn't worth pursuing in general because it wouldn't be very useful. Possibly there were other technical difficulties encountered, but I don't recall at the moment. At any rate, I don't feel compelled to pursue this in 1.0.
When introducing the message entity in #1, we considered the possibility of a message thread entity relationship. Somehow I didn't end up discussing it at all in the ticket though. I'm not sure if it would really be useful or not, but I wanted to note that I'd created this class for it, if we ever revisit this:
The text was updated successfully, but these errors were encountered: