fix: minor fixes for client side datasets api migration v3 to v4

[Junjiequan]

Description

• v4 datasets.findAll takes raw mongo operators, but JSON has no date type, so the client sends {$gte: {$date: "..."}}. nothing converts that marker, so it reached mongo as a plain object instead of a Date and the filter matched nothing. castWhereFilter converts it before the pipeline runs, and is written as a marker map so other extended json types can be added later
• add date.begin and date.end only when a value is provided
• added 3 allowed filter keys to keep the query consistent with v3 behavior: $text, $search, $date

Additional bug fix:

• fixed a param name mismatch between @ApiParam and the route on the attachment delete endpoint, which was generating a not needed required id field in the sdk

Motivation

Fixes

• Bug fixed (#X)

Changes:

• changes made

Tests included

• Included for each change/fix?
• Passing?

Documentation

• swagger documentation updated (required for API changes)
• official documentation updated

official documentation info

Summary by Sourcery

Fix dataset filter handling and attachment API metadata for the v3-to-v4 client migration.

Bug Fixes:

• Convert extended JSON date markers in dataset filters into BSON dates so date-based queries work correctly.
• Allow partial date ranges by only applying provided begin and end bounds.
• Correct the attachment deletion API parameter metadata to match the route and prevent an extraneous SDK field.

Enhancements:

• Expand supported dataset filter operators to preserve v3-compatible query behavior.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook