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
Moving the resolvedStatus within the ThreadListFilter type
When adding the `resolvedStatus` to the LocationData API, I noticed that it wasn't relevant
to the ThreadList, as the ThreadList doesn't have pagination and fetches all threads anyway - doing
all filtering within the component. So I created a union type. This is not great 1. because it doesn't
enforce consistency in our API filters, and 2. because the docs look bad (I had not noticed). TsDoc
can't handle union types and it's a known bug (microsoft/tsdoc#164). This
PR moves the `resolvedStatus` within the ThreadListFilter type, then goes through all its uses and
decides on whether to omit it or not.
Test Plan:
Tested ThreadedComments with all 4 tab options and they worked correctly. Then tested the
ThreadedComments by switching the underlying API to use the deprecated parameter, which also worked
as expected.
Also, docs look really nice again :)
Reviewers: flooey, jwatzman, km-nur
Reviewed By: km-nur
Pull Request: https://github.com/getcord/monorepo/pull/6436
monorepo-commit: e8a3e6ed8846cff9baeffc16e7e1dabdb7e42cb7
0 commit comments