Project direction and Permission Management Improvements

[KursatKonak]

Hello, using this template as a base and improving based on our requirements creates a good amount of divergence. I already implemented Transactional Outbox as Keyed because having outbox per module kept them decoupled. A central outbox needs all the modules that use it active. It's not right or wrong, just an architectural preference.

So now my codebase is already diverged from original repository 🤔

So to keep my base 'aligned' with FSR base to keep improving i wanted to create an issue and discuss it out and get your perspective.

I got another example now regarding permissions i wanted to share before going out and 'fixing' it.

• Top bar shows chat, notification button, search etc. by default, but if their API endpoints have permission requirements, API backend is throwing a lot of unnecessary exceptions. Client should have not sent those requests based on perms in the first place.
• All users have this overview page in dashboard with a lot of widgets, but widget visibility / query-call are not tied to perms, this also causes a lot of exceptions.
• Permissions are not an array but magic strings and not created in a single way, this will inevitably cause some mistyping along the way, see an example below. I think explicit - dynamic naming is very useful, but i would like to retain them in one place instead of copy pasting this magic strings all over the place

const Permissions = {
  Chat_Channels_View: "Permissions.Chat.Channels.View",
} as const;

function hasPermission(permissionName: string, permissions: readonly string[]): boolean {
    if (permissionName && !permissions.includes(permissionName)) return false;
    // if (item.anyPerm && !item.anyPerm.some((p) => permissions.includes(p))) return false;
    return true;
}

{hasPermission("Permissions.Chat.Channels.View", perms) && (
    <ChatUnreadBadge />
)}

to

{hasPermission(Permissions.Chat_Channels_View, perms) && (
    <ChatUnreadBadge />
)}