-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Don't use reports for isArchived Check #54590
Comments
@srikarparsi Can contributor work on this? |
Hey @nkdengineer, actually have a WIP PR here that I've been working on on the side. |
@srikarparsi, @allgandalf Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@srikarparsi, @allgandalf Eep! 4 days overdue now. Issues have feelings too... |
@srikarparsi, @allgandalf 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
Working on this here |
@srikarparsi, @allgandalf Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@srikarparsi, @allgandalf 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
@srikarparsi, @allgandalf Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it! |
Almost done, hopefully can be merged tomorrow |
As a part of the migration to start using the
reportNameValuePairs
Onyx collection in App, we migrated theprivate_isArchived
key from the reports collection to thereportNameValuePairs
collection.To finish this migration, we need to stop reading from the
reports
collection here and instead use thereportNameValuePairs
collectionThe text was updated successfully, but these errors were encountered: