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
Batch operations #256
Batch operations #256
Conversation
setCellContent: (address: SimpleCellAddress, newCellContent: RawCellContent) => void, | ||
setCellContents: (topLeftCornerAddress: SimpleCellAddress, cellContents: RawCellContent[][] | RawCellContent) => void, |
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.
@swistak35 Do we need the BatchExecutor
in batch
method? This create sync problem and with suspendEvaluation
we're using engine instance anyway. Shouldn't all (or most of) engine public APIs be available to run in batch
?
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.
@wojciechczerniak yes, this is very possible, I just like to get to removals incrementally, but was thinking the same
ca1c90b
to
480e320
Compare
We no longer have more evaluators and I don't think we will have in near future
Temporarily. I want to have unified interfaces in both CrudOperations and HyperFormula is intermediary step before removing CrudOperations.
…onIsNotSuspended All suspension code was already renamed to use "evaluation suspension" language
7189892
to
60d4d77
Compare
Context
How has this been tested?
Types of changes
Related issue(s):
Checklist: