sure, here's one: updating tabs style.

tabs have a new style, and we have a central library for all styles and components we use across the projects such as buttons, dropdowns, inputs.. etc.

So I created a class for the tabs with the new style, she disagreed saying that it should be two components, one for the wrapper <nav><ul></ul></nav> and one for the inner tabs, I thought that this is an overkilll and that enforcing the structure can be done through reviews, it's not like we build tabs every day, we only had two of them ever, but I ended up doing it, and to make the component more useful I made the inner component check if the tab is active optionally so the user of the component doesn't need to do that logic every time we use it.

She disagreed again, saying that we may want to add target="_blank" or anything to the inner component, so it should be passed in as a slot (we're using vue.js), I disagreed this time saying that if we want this level of flexibility and access to the inner component, we should use a class instead of two useless components as it's a lot more hassle to import two components and use them, and they make unit testing a lot more complicated, she disagreed saying we need to enforce the structure and that adding components just for style is ok, when I disagreed again she asked other developers to take a side, no one sided to either for us and they just mentioned the pros and cons of each approach.

I ended up redoing the simple class into two components, then redoing the inner component into a hollow slot while I don't agree with any of this.