would it be possible to move this to a User model method instead?

Hey @CvX I took a look at this and tried to refactor as you asked.

This function is generic and works for multiple types of user models (user, post action user, post reader) so I would need to duplicate the logic. Apart from that, some of these models are not explicit defined (ie:post action user).

Let me know if you still think it is better to move or if you have any other idea.

Ok, so let's move it to lib directory. Services are a better fit for stuff with state and/or multiple related methods (used by various components, etc) but here we have just a single-input utility function.

also, can you rename atts to attrs? 😅 that contraction is way more common in core

@CvX as we discussed in chat, I replaced the implementation to use Value Transformers and it works like a charm! thank you for the tip 👯