MongoGenericRepository 12.2.0

• .NETStandard 2.1

  • Microsoft.Extensions.Options (>= 10.0.12)
  • MongoDB.Driver (>= 3.12.0)

• net10.0

  • Microsoft.Extensions.Options (>= 10.0.12)
  • MongoDB.Driver (>= 3.12.0)

• net8.0

  • Microsoft.Extensions.Options (>= 10.0.12)
  • MongoDB.Driver (>= 3.12.0)

• net9.0

  • Microsoft.Extensions.Options (>= 10.0.12)
  • MongoDB.Driver (>= 3.12.0)

The entity's key is no longer trimmed on write.

   Fixed:
   - Add, AddRange and both Update overloads trimmed every string property, the Id included. A key with surrounding whitespace was stored under a trimmed key the caller did not hold, while Get, Delete and the id filters never trimmed. The Id and whichever member the serializer stores as _id are now written and matched exactly as passed.
   - Update filtered on the trimmed key, so it missed a document stored under the untrimmed one and, with IsUpsert, created a second document. It now matches by the untouched key; the same applies to the bulk Update.
   - AddRange and the bulk Update enumerate their sequence once. A lazy projection used to run twice: AddRange inserted untrimmed copies, and a mutating projection applied its change twice.
   - Static string properties are no longer trimmed.

   Added:
   - [NoTrim] keeps a string property out of the trimming, for values whose whitespace carries meaning: natural keys outside the id, hashes, signatures.

   Behaviour change:
   - Only keys with leading or trailing whitespace are affected. Documents written by earlier versions are stored under the trimmed key: an Update built from untrimmed input now misses them and, with IsUpsert, creates a second document. Normalise keys before building them if that is what you want.

   See CHANGELOG.md for the full notes.