Skip to content

Conversation

CarloMariaProietti
Copy link
Contributor

Solves issue #1021. It comes with a test case which is inspired by after's test case.

@Jolanrensen Jolanrensen self-requested a review October 6, 2025 12:27
Copy link
Collaborator

@Jolanrensen Jolanrensen left a comment

Choose a reason for hiding this comment

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

Thanks! It works perfectly :)

Please also run gradlew apiDump and commit the changes.


@Deprecated(DEPRECATED_ACCESS_API)
@AccessApiOverload
public fun <T, C> MoveClause<T, C>.before(column: AnyColumnReference): DataFrame<T> = before { column }
Copy link
Collaborator

Choose a reason for hiding this comment

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

no need to add these deprecated overloads :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'll remove them

return removeResult.df.insertImpl(toInsert)
}

// move target after last of toInsert
Copy link
Collaborator

Choose a reason for hiding this comment

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

could you expand this doc a bit? I have a bit of a hard time understanding the logic below.

so... you insert the removed columns after the target column in the first place, and then you move the target column after the removed/inserted columns?

That's... really clever :D

But it took me a while to get it :) so please expand the doc a tiny bit :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thank you very much, I appreciate it. That's exactly the logic. I'll try to make the doc more undesrtandable.

@CarloMariaProietti
Copy link
Contributor Author

I implemented requested changes, In addition I noticed a bug when the function throws exception, so i fixed it.

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.

2 participants