Rename toArray
to arrayFromSet
and simplify export
syntax
#550
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.
As @alessbell has reported in codesandbox/sandpack#940, it appears Sandpack may have a transpiler bug when compiling the following code:
It's understandable the combination of
export
, destructuring, renamingfrom: toArray
, and a default expression would be unusual enough to have escaped testing, but this works with other transpilers, and is valid TypeScript (and should compile to equivalent valid JS).What happens, specifically, is that
exports.toArray
never gets assigned likeexports.hasOwnProperty
andexports.maybeUnsubscribe
, presumably becausetoArray
is not detected as an exported identifier.Fortunately, there's another way of writing this code that should be less challenging to transpile:
I took this opportunity to rename the helper function from
toArray
toarrayFromSet
, reflecting the fact that we use this function only for converting sets to arrays, which allows us to keep the fallback function simple (for use whenArray.from
is not available).