Bike shedding code style is more likely to be the narrow problem that has no influence on the bigger picture.

I don't care how shitty your code looks, I see little risk as long as it has well contained boundaries with system at large.

You have ownership of your module, and if you leave, and someone needs to work on it, and cringes at how it looks, since the input/output edges are clear, it can be thrown out at re-written to said dev's personal taste.

Focus on delivering business value and creating the best END-USER experience.

If you are focused on pretty code, you will likely be the only one patting yourself on the back when all is said and done.