Repository navigation
fix: proper Typescript typings for Seq.concat() - #2040
Merged
jdeniau merged 1 commit intoJan 11, 2025
Merged
jdeniau merged 1 commit into
jdeniau merged 1 commit into
Conversation
Copy link
Copy Markdown
Sorry, something went wrong.
alexvictoor
force-pushed
the
fix-seq-typings
branch
from
a9595fe to
cc87630
Compare
December 9, 2024 13:02
Merged
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 PR fixes an issue occurring when a sequence is typed as a regular Seq (not an IndexedSeq, keyedSeq, ...).
Below a code fragment to reproduce the issue: