-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
See extra fields per chat #3095
Conversation
Still some discussion on this one, keeping it a draft. |
Going to figure out how/if I can do unit tests for this one. |
…to amal-chattype-info
…to amal-chattype-info
Ooops it looks like I double dipped in puller-bear sorry @AndrewGable. |
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Deployed to staging in version: 1.0.65-1🚀
|
🚀 Deployed to production in version: 1.0.68-4🚀
|
@stitesExpensify, please review
CC: @yuwenmemon
Details
This sets up information used in default room type chats.
Fixed Issues
Fixes https://github.com/Expensify/Expensify/issues/161776
Tests
Tested that this change lets you load reports and doesn't cause the app to crash, since we don't have any front end changes for this feature yet.
QA Steps
report_
go through a few of the options and verify that ownerEmail, policyID, and chatType are there in the object (see screenshot for reference)Tested On
Screenshots
Essentially just checking that the values: ownerEmail, policyID, and chatType are set in localstorages. They'll be used in a later PR.
Web, Mweb, and Desktop