Open danry25 opened 4 months ago
Yeah dev oversight on this one. First, I've already moved the start conversation out of the threadpreview container to make it accessible since it's the current workaround. Second, I've removed a 25 result limit on the query we use to build the threadpreview components. (this does mean users with a ton of conversations will have a massive page load time but that's why I'm working on the "search for conversation" view) After we've got the new search view finished I want to implement a backfill conversations functionality similar to how we backfill messages in the thread view
The filter threads by contact name or number feature is live.
I've got the search database and initial limit implemented. Still working on the lazy loading aspect. For the message search do you want to have search all threads and search specific threads (one would be in the ThreadSearch component the other would be in the conversation component )
When a Web Texting instance has many existing conversations, it is hard to view older conversations unless you know the phone number your looking to view and you send them a new message.
Goals: