[Data] Refactor Threads in lists

[theurbanforrest]

Story

Dev: Threads in lists are starting to get unwieldy. We have many different ThreadsLists so should consolidate into a single component controlled by props

Acceptance Criteria

Consolidate all ThreadsLists into single component

[theurbanforrest]

Proposed Solution

For our new ThreadsList component:

general

• will use withFirebase , withAuthentication , and withAuthorization to leverage firebase + local state

props

• users - array of userUid's. List returns only for these users *statuses - array of statuses. List returns only for these statuses. When used in conjunction with users, works like an AND statment

other

• Admin-related functions (i.e. Hide, Unhide) will leverage withAuthorization for logic

[theurbanforrest]

Resolved in https://github.com/theurbanforrest/olomana/commit/3039adf4214689f1897f40712492f6582076581e

Summary

Implemented new component ThreadsList and deleted duplicative & verbose code that it now replaces

props

• statuses - implemented as described above
• users - implemented as described above
• ctaView - View CTA to /thread/:uid
• ctaEdit - Edit CTA to /thread/:uid/edit -- only renders if you own the Thread
• ctaUnhide - Unhide CTA to prompt unhide flow -- only renders if you're Admin
• authUser - Always required, given that render() errors if not present

Future

• Figure out how to code without requiring authUser

[theurbanforrest]

Minor formatting updates in https://github.com/theurbanforrest/olomana/commit/1cd4b2a17370c18c4ef9d28a0c456def70e8465e , related to this issue #23