feat: add xlsx and icalc import export methods#379
Closed
BrianHung wants to merge 2 commits into
Closed
Conversation
Contributor
Author
|
Would probably close this PR in favor of #381 which separates the calc engine from xlsx handling in a separate wasm file. That does require two separate calls to init now. |
Member
|
Hi @BrianHung, closing this in favour of #381 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This does increase the package size from 2.4 mb to 3.7 mb. Alternatives would be to create wasm bindings for xlsx specifically (although that might run into js -> wasm conversion issues now), or to create a separate ironcalc-xlsx.wasm build and keep the normal ironcalc.wasm.