Having someone else implement the fix and take ownership of the code is a positive in the long term, unless you're committed to the project - in which case you

Having someone else implement the fix and take ownership of the code is a positive in the long term, unless you're committed to the project - in which case you ought to be fine with looking at and fixing other bugs. In a company context, you'd expect the reviewer to coach someone being onboarded towards a solution the reviewer prefers, but that's because you know the person is going to be around for a while, and they're going to need to take ownership. If you aren't in it for the long haul, you shouldn't expect your code contributions to stick.