-
Notifications
You must be signed in to change notification settings - Fork 572
fix(compat/dropRight): clean up JSDoc by removing duplicate overload and guard param #1789
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
Open
Antoliny0919
wants to merge
2
commits into
toss:main
Choose a base branch
from
Antoliny0919:update-drop-right-doc
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+5
−23
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -10,40 +10,22 @@ import { toInteger } from '../util/toInteger.ts'; | |
| * of elements removed from the end. | ||
| * | ||
| * @template T - The type of elements in the array. | ||
| * @param collection - The array from which to drop elements. | ||
| * @param array - The array from which to drop elements. | ||
| * @param itemsCount - The number of elements to drop from the end of the array. | ||
| * @param [guard] - Enables use as an iteratee for methods like `_.map`. | ||
| * @returns A new array with the specified number of elements removed from the end. | ||
| * | ||
| * @example | ||
| * const array = [1, 2, 3, 4, 5]; | ||
| * const result = dropRight(array, 2); | ||
| * // result will be [1, 2, 3] since the last two elements are dropped. | ||
| */ | ||
| export function dropRight<T>(array: ArrayLike<T> | null | undefined, n?: number): T[]; | ||
| export function dropRight<T>(array: ArrayLike<T> | null | undefined, itemsCount?: number): T[]; | ||
|
|
||
| /** | ||
| * Removes a specified number of elements from the end of an array and returns the rest. | ||
| * | ||
| * This function takes an array and a number, and returns a new array with the specified number | ||
| * of elements removed from the end. | ||
| * | ||
| * @template T - The type of elements in the array. | ||
| * @param collection - The array from which to drop elements. | ||
| * @param itemsCount - The number of elements to drop from the end of the array. | ||
| * @param [guard] - Enables use as an iteratee for methods like `_.map`. | ||
| * @returns A new array with the specified number of elements removed from the end. | ||
| * | ||
| * @example | ||
| * const array = [1, 2, 3, 4, 5]; | ||
| * const result = dropRight(array, 2); | ||
| * // result will be [1, 2, 3] since the last two elements are dropped. | ||
| */ | ||
| export function dropRight<T>(collection: ArrayLike<T> | null | undefined, itemsCount = 1, guard?: unknown): T[] { | ||
| if (!isArrayLike(collection)) { | ||
|
Comment on lines
-40
to
-43
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I noticed that most implementation signatures also include JSDoc. Is there a reason we document those as well? |
||
| export function dropRight<T>(array: ArrayLike<T> | null | undefined, itemsCount = 1, guard?: unknown): T[] { | ||
| if (!isArrayLike(array)) { | ||
| return []; | ||
| } | ||
| itemsCount = guard ? 1 : toInteger(itemsCount); | ||
|
|
||
| return dropRightToolkit(toArray(collection), itemsCount); | ||
| return dropRightToolkit(toArray(array), itemsCount); | ||
| } | ||
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 noticed that many other places also expose the guard parameter in the JSDoc. Is there a reason for documenting guard explicitly?
As described in the docs, I understand that it's there to support cases where the function is passed as an iteratee to methods like map(for Lodash compability...), but I'm wondering if this is something users actually need to know about.
Would it be better to keep this as an internal implementation detail?