Leaking partner field names through the whole codebase couples you to an external contract you do not control.
Naming the pitfall early helps you design tests, reviews, and safer boundaries. Connect the idea to a realistic coding decision so recall is easier when solving similar questions.