Address reasons why we do not use object authorization on BoardListType
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
We want to always use object authorization, unless there are compelling technical reasons why it is impossible, since this is much safer.
It is possible that this has been disabled for performance reasons, which we can probably address with judicious preloading during authorization (and maybe some light support for this at the DSL level)
The following discussion from !67909 (merged) should be addressed:
-
@alexkalderimis started a discussion: (+2 comments) I was going to suggest that this check is unnecessary since it would be handled by
BoardListType, but I see thatBoardListTypedoes not have an authorization set.Do you know why that is? It there a performance issue we have to work around? (if so, we probably should create technical debt issue and link to it in a comment here)
If not, then we can remove this method.
/cc @egrieff