Add properties in Evaluation Result - Custom Evaluator extra fields.

[w-javed]

No description provided.

[Copilot]

Pull request overview

Adds support for passing through custom evaluator “extra fields” via a properties bag into the AOAI-style evaluation result objects produced by the evaluation results converter.

Changes:

• Update _extract_metric_values to detect an outputs.<criteria>.properties dict and propagate it onto per-metric extracted values.
• Update _create_result_object to include properties in the final AOAI result payload when present.
• Add a unit test asserting properties is preserved and not flattened into the top-level result object.

Reviewed changes

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

File	Description
sdk/evaluation/azure-ai-evaluation/azure/ai/evaluation/_evaluate/_evaluate.py	Propagates a per-criteria properties dict into per-metric result objects during AOAI conversion.
sdk/evaluation/azure-ai-evaluation/tests/unittests/test_evaluate.py	Adds coverage validating properties passthrough behavior for a custom evaluator result row.

[nagkumar91]

Review — Properties passthrough

1. Shared dict reference (bug-risk) — In _extract_metric_values, the same properties object is assigned to every metric entry:

for metric_dict in result_per_metric.values():
    metric_dict["properties"] = properties  # same object reference

If anything downstream mutates one entry's properties, all entries are affected. Consider metric_dict["properties"] = properties.copy() (or copy.deepcopy if nested dicts matter).

2. No test for the warning path — The isinstance(metric_value, dict) guard logs a warning when properties isn't a dict, but no test covers this branch. A quick test passing properties="not_a_dict" would confirm the warning fires and properties is omitted.

3. Typo fixes in _base_rai_svc_eval.py — Good catch on self._eval_metric. value → self._eval_metric.value. Cosmetic (Python allows whitespace after dot) but worth cleaning up.