Fix Dataset.map to handle non-DataArray outputs #10839
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #10835
Summary
After PR #10602,
Dataset.mapstarted failing when functions returned non-DataArray values (e.g., scalars), raisingAttributeError: 'int' object has no attribute 'coords'when trying to access.coordson the returned values.This PR restores backward compatibility by converting non-DataArray outputs to DataArrays before accessing their
.coordsattribute.Changes
Dataset.mapto check if returned values are DataArrays and convert them if notTest plan
test_map_non_dataarray_outputscovering scalar outputs, numpy arrays, and mixed casesDataset.maptests passtest_dataset.pypass (495 passed)🤖 Generated with Claude Code