-
Notifications
You must be signed in to change notification settings - Fork 3.9k
OptimisticReportNames: Working updates cache #70870
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
Closed
sosek108
wants to merge
8
commits into
Expensify:main
from
callstack-internal:feat/3-report-name-value-pairs
Closed
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
c8e1942
handle reportNameValuePairs in OptimisticReportNames
sosek108 add0d60
Working updates cache
sosek108 c597e6e
typecheck fixes
sosek108 b842145
Merge branch 'main' into feat/3-report-name-value-pairs
sosek108 7f456b3
Merge branch 'main' into feat/3-report-name-value-pairs
sosek108 9d15923
Apply modifications from comments.
sosek108 d9d955e
Merge branch 'main' into feat/3-report-name-value-pairs
sosek108 a7aa0a7
test fix
sosek108 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have to ensure, that transaction that we're trying checking is most up to date. If there were any previous updates to transaction the cached transaction is the most up to date.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, so why can't we always get the transaction from the cache, instead of starting with the FormulaContext value, then falling back to the cache, then the transaction currently stored in Onyx?
Isn't the formula context transaction always the same as the one in the cache?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, context's transaction is from cache ☝️.