Repository navigation
feat(memory): [1/3] add fieldMatching to memory search settings [ECS-2116] - #1943
Conversation
…2116] Memory search matched when any one field passed its threshold. ECS now accepts settings.fieldMatching (or | and, default or); expose it on SearchSettings so callers can request AND matching. Bumps uipath-platform to 0.2.39. ECS-2116
981bd82 to
bf273b9
Compare
There was a problem hiding this comment.
🟡 Changes recommended
Serialized field-matching casing needs reconciliation with the wire contract stated in the PR description.
1 open finding
What changed in this PR
Adds configurable field matching to the platform SDK’s memory search settings, preparing for downstream integrations.
Changes:
- Exports
FieldMatchingand addsSearchSettings.field_matching, defaulting to OR. - Adds request-serialization assertions for default and explicit matching.
- Bumps
uipath-platformto 0.2.39 and updates lockfiles.
| File | Description |
|---|---|
| packages/uipath/uv.lock | Updates platform dependency version. |
| packages/uipath-platform/uv.lock | Updates platform package version. |
| packages/uipath-platform/tests/services/test_memory_service.py | Covers field-matching serialization. |
| packages/uipath-platform/src/uipath/platform/memory/memory.py | Defines matching enum and search setting. |
| packages/uipath-platform/src/uipath/platform/memory/__init__.py | Exports FieldMatching. |
| packages/uipath-platform/pyproject.toml | Bumps version to 0.2.39. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
🚨 Heads up:
|
| [[package]] | ||
| name = "uipath-platform" | ||
| version = "0.2.38" | ||
| version = "0.2.39" |
There was a problem hiding this comment.
don't we need to update the uipath pyproject.toml to reflect this?
There was a problem hiding this comment.
No. packages/uipath resolves uipath-platform from the local path via [tool.uv.sources], so its lock follows the workspace version on every platform bump. Its pyproject.toml floor (>=0.2.37) only needs raising when uipath itself starts using new platform API, and nothing in uipath uses FieldMatching. Same shape as the last platform-only bump, #1939: platform pyproject plus both locks, uipath pyproject untouched.




Memory search matched when any one configured field passed its threshold, so an escalation saved for one customer could be recalled for another. ECS now accepts
settings.fieldMatchingwith values or/and, default or (UiPath/vdbs#2882). ECS parses the value case-insensitively.This exposes
field_matchingonSearchSettingsasfieldMatching, serialized asOr/Andwith the same casing assearchModeand as the Agents dotnet client. Defaults toOr, so existing callers are unchanged. Bumps uipath-platform to 0.2.39. Part 1 of 3; uipath-langchain and uipath-agents follow once this publishes.Dotnet counterpart: UiPath/Agents#6675. Ticket: https://uipath.atlassian.net/browse/ECS-2116