fix(document): handle nested paths in optimisticConcurrency include/exclude

[mahmoodhamdi]

Problem

When using optimisticConcurrency with include arrays or exclude objects, nested paths are not handled properly.

Exclude case: Excluding profile does not exclude profile.firstName. Modifying profile.firstName still triggers versioning even though its parent is excluded.

const userSchema = new Schema({
  profile: profileSchema,
  balance: Number
}, { optimisticConcurrency: { exclude: ['profile'] } });

user.profile.firstName = 'Bob';
user.$__delta();
// BUG: user.$__.version === VERSION_ALL
// EXPECTED: user.$__.version === undefined

Include case: Including profile.address.country does not trigger versioning when setting profile.address (the parent).

Root Cause

The existing code uses Set.has() for exact path matching, which doesn't account for parent-child path relationships.

Solution

Added two helper functions:

• _isExcludedByOptCon(path, excludeSet): a path is excluded if it matches exactly OR any of its parent prefixes is in the exclude set (e.g. profile excludes profile.firstName)
• _isIncludedByOptCon(path, includeSet): a path is included if it matches exactly, OR any parent prefix is included, OR any included path is a child of the modified path (e.g. modifying profile.address triggers when profile.address.country is included)

Testing

Added 5 new test cases in test/versioning.test.js covering:

1. Exclude: parent exclusion cascades to children
2. Exclude: non-excluded paths still trigger version alongside excluded children
3. Include: parent inclusion cascades to children
4. Include: modifying parent triggers when child is included
5. Include: non-included nested paths don't trigger

All 22 optimisticConcurrency tests pass.

Fixes #16054

[Copilot]

Pull request overview

This PR fixes optimisticConcurrency path matching so include/exclude configurations correctly account for nested path relationships (parent ↔ child), addressing gh-16054.

Changes:

• Update Document#$__delta() optimistic concurrency checks to treat nested paths as relevant when appropriate (prefix/descendant matching rather than exact Set.has()).
• Add internal helpers for include/exclude nested-path evaluation.
• Add a focused test suite for nested include/exclude behavior in optimistic concurrency.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
lib/document.js	Implements nested-path aware include/exclude checks for optimistic concurrency in $__delta() via new helper functions.
test/versioning.test.js	Adds regression tests covering nested include/exclude behavior for optimistic concurrency.

[vkarpov15]

A couple of performance related suggestions.

[vkarpov15]

Need to make sure to check if path contains '.' before splitting for performance

[vkarpov15]

I'd like to see if there is a way to reuse split values in this function similar to hasIncludedChildren for projections in lib/document.js. This check is very expensive - lots of split() calls, loops. It would be ideal to avoid this by precomputing the split values from this.$__schema.options.optimisticConcurrency