fix: prevent negative slice index in populate subdocPath calculation #15862
+3
−3
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.
Description
This PR fixes a bug where calculating
subdocPathin populate operations could result in negative slice indices, causing incorrect path calculations.Fixes #15861
Problem
In
lib/helpers/populate/getModelsMapForPopulate.js, lines 242, 304, and 325 use:If
schema.path.length + 1 >= options.path.length, the second argument becomes negative, causingslice()to count from the end instead of the beginning.Solution
Added
Math.max(0, ...)to ensure the slice index never goes negative:Changes
Math.max(0, ...)wrapperMath.max(0, ...)wrapperMath.max(0, ...)wrapperTesting
test/model.populate.test.js)npm run lint)Impact
This fix prevents incorrect subdocPath calculations in edge cases where the schema path is longer than or equal to the options path, ensuring populate operations work correctly in all scenarios.