Why I break the Sprint Review done rule

There's one Scrum rule I always loved to break : in a Sprint Review, you only demo what is "Done". 💁🏻‍♂️
⠀
I'm not saying you should pretend something is done and ready to use when it's totally not the case. That's the fastest way to lose the trust of your stakeholders (and good luck getting it back 😅).
⠀
But by default, a rule that tells you to NOT show something, and therefore delays the feedback you could get, is inherently a rule that I will want to break. Why would you wait a whole Sprint to hear "hmm, that's not really what we meant"?
⠀
So show it. Half-baked, with dummy data, without the nice UI... whatever. Just say it clearly : this part works, this part is fake, this part is not there yet.
⠀
Worst case, you got your feedback earlier. 🤷🏻‍♂️
⠀
However, if you feel like you need to do this every Sprint, you might ask yourselves the question : did we split our items correctly?