Skip to content

Conversation

AndreiKingsley
Copy link
Collaborator

@AndreiKingsley AndreiKingsley commented Mar 14, 2025

Fixes #896.

Now Map is treated like value class and not unfolded. Also fix unfolding behavior in unfold (now it's the same as in toDataFrame())

this in valueTypes ||
this.isSubclassOf(Number::class) ||
this.isSubclassOf(Enum::class) ||
this.isSubclassOf(Map::class) ||
Copy link
Collaborator

@koperagen koperagen Mar 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not consistent with plugin - here it's all subclasses, in plugin only Map and MutableMap specifically. Which one should it be?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would do it like the plugin. There are many classes that have List or Map as supertype but they should probably be treated like a normal class.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only Map and MutableMap. Fixed.

@Jolanrensen Jolanrensen self-requested a review March 14, 2025 12:42
)

/**
* Check
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

check what? ;P


/**
* Check
*/
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

very clean solution :)

@AndreiKingsley AndreiKingsley merged commit 5091e23 into master Mar 17, 2025
3 checks passed
@AndreiKingsley AndreiKingsley deleted the map_unfold branch March 17, 2025 09:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

unfold / toDataFrame behavior for Maps
3 participants