This repository has been archived by the owner on Oct 22, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 87
separated
method added in Iterable extension
#343
Closed
kishan-dhankecha
wants to merge
1
commit into
dart-archive:master
from
kishan-dhankecha:seprated_extension_method
Closed
Changes from all commits
Commits
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 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 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 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
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.
I don't think this version is flexible enough.
The use-cases I've heard mentioned won't all be satisfies by inserting the same value every time, and the typing might not work out.
I'd at least want a version where the separator is generated each time.
Then it could be generated based on position, or on adjacent values.
Something like these would cover those:
and possibly also:
The
separatedBy
andseparatedByIndex
might be combined into one, it's easy to ignore an argument, and cheap to increment an integer.I'd expect the separator to not always have the same type as the elements being separated. (A
List<TextWidgets>
cannot be separated bySeparatorWidget
s, one would have to first copy the text widgets into aList<Widget>
and then separate them)That makes a top-level function more useful (or stastic function or constructor, if we could add such using extensions):
Maybe we can make the separator optional, like:
where returning
null
means no separator.(Consider:
separatedOptionalByElements(pathSegments, (before, after) => before.endsWith('/') || after.startsWith('/') ? null : '/')
where we only insert a separator where it's needed. Maybe this is too specialized, and ajoin
with conditional separator would be more relevant.)