Samuele Lorefice REDCODE
  • Joined on 2024-01-01
REDCODE commented on pull request MilkyShots/MilkyShots#125 2026-07-14 16:39:13 +00:00
feat: #106 auth/permissions redesign — 5-actor model, #93 visibility levels (backend)

As said above, pageSize should use the const in PagedSearchParams as default.

REDCODE commented on pull request MilkyShots/MilkyShots#125 2026-07-14 16:39:13 +00:00
feat: #106 auth/permissions redesign — 5-actor model, #93 visibility levels (backend)

I'm not 100% sure about having the mapper do the access level filtering. @Fastwind what is your opinion here?

REDCODE commented on pull request MilkyShots/MilkyShots#125 2026-07-14 16:39:13 +00:00
feat: #106 auth/permissions redesign — 5-actor model, #93 visibility levels (backend)

No check for deleted, which should be admin only.

REDCODE commented on pull request MilkyShots/MilkyShots#125 2026-07-14 16:39:13 +00:00
feat: #106 auth/permissions redesign — 5-actor model, #93 visibility levels (backend)

Additionally passing a bool breaks convention, rather accept the enum value of user role

REDCODE commented on pull request MilkyShots/MilkyShots#125 2026-07-14 16:39:13 +00:00
feat: #106 auth/permissions redesign — 5-actor model, #93 visibility levels (backend)

Not sure this is correct either. Persons are visible depending from their visibility, maintainers get a free pass, but only for the persons they are a maintainer of. Currently the code seems to allow maitainers to see all persons regardless of them being a maintainer of them or not

REDCODE commented on pull request MilkyShots/MilkyShots#125 2026-07-14 16:39:13 +00:00
feat: #106 auth/permissions redesign — 5-actor model, #93 visibility levels (backend)

As said before, the same error happens here. Maintainers shoudl be able to see all assets of the people they are a maintainer of.

REDCODE commented on pull request MilkyShots/MilkyShots#125 2026-07-14 16:39:13 +00:00
feat: #106 auth/permissions redesign — 5-actor model, #93 visibility levels (backend)

Stats repository should return also a protected assets stats.

REDCODE commented on pull request MilkyShots/MilkyShots#125 2026-07-14 16:39:13 +00:00
feat: #106 auth/permissions redesign — 5-actor model, #93 visibility levels (backend)

Maintainer should be able to see the visibility if it's an asset assigned to a cosplayer they maintain

REDCODE commented on pull request MilkyShots/MilkyShots#125 2026-07-14 16:39:13 +00:00
feat: #106 auth/permissions redesign — 5-actor model, #93 visibility levels (backend)

Maintainer of a person should also get this value

REDCODE commented on pull request MilkyShots/MilkyShots#125 2026-07-14 16:39:13 +00:00
feat: #106 auth/permissions redesign — 5-actor model, #93 visibility levels (backend)

Visibility field is missing?

REDCODE commented on pull request MilkyShots/MilkyShots#125 2026-07-14 16:39:13 +00:00
feat: #106 auth/permissions redesign — 5-actor model, #93 visibility levels (backend)

Filtering by access level? As the other search query methods do? Maybe? Not sure.

REDCODE commented on pull request MilkyShots/MilkyShots#125 2026-07-14 16:39:13 +00:00
feat: #106 auth/permissions redesign — 5-actor model, #93 visibility levels (backend)

Maintainer OF that cosplayer can get all assets, otherwise it's like an user.

REDCODE commented on pull request MilkyShots/MilkyShots#125 2026-07-14 16:39:13 +00:00
feat: #106 auth/permissions redesign — 5-actor model, #93 visibility levels (backend)

Yes they can, if they are a maintainer of the cosplayer related to the album.

REDCODE commented on pull request MilkyShots/MilkyShots#125 2026-07-14 16:39:13 +00:00
feat: #106 auth/permissions redesign — 5-actor model, #93 visibility levels (backend)

Maintainer is missing here.

REDCODE commented on pull request MilkyShots/MilkyShots#125 2026-07-14 16:39:13 +00:00
feat: #106 auth/permissions redesign — 5-actor model, #93 visibility levels (backend)

if we are just trying to access media, and we will have to check user being able to access the asset, this includes the user being a maintainer of the cosplayer the asset is assigned to... do we need the media repository to also get the visibility level?

REDCODE commented on pull request MilkyShots/MilkyShots#125 2026-07-14 16:39:13 +00:00
feat: #106 auth/permissions redesign — 5-actor model, #93 visibility levels (backend)

This query needs a double check.

REDCODE pushed to feature/106-auth-redesign at MilkyShots/MilkyShots 2026-07-14 16:13:20 +00:00
1b444dab93 feat(auth): complete Maintainer role — add PersonMaintainer checks, update controller authz, pass uploadedBy search param
REDCODE created branch feature/106-auth-redesign in MilkyShots/MilkyShots 2026-07-14 15:52:26 +00:00
REDCODE pushed to feature/106-auth-redesign at MilkyShots/MilkyShots 2026-07-14 15:52:26 +00:00
50bf0a2a78 feat(db): add migration for auth redesign — drop IsPubliclyShared/UserOwnerId/SharedWith, add Visibility, PersonMaintainer, rename OwnerId→UploadedBy
2335e8e23a feat(repos,controllers): update repositories, interfaces, controllers for auth redesign — visibility filtering, UploadedBy/Uploader rename, Maintainer support
d02a010083 feat(infra): update DbContext and mappers for auth redesign — new relationships, PersonMaintainer, conditional Visibility
6676347353 feat(models): update models for auth redesign — rename Owner→UploadedBy, drop UserOwnerId/IsPubliclyShared, add EVisibility, PersonMaintainer
c9391d840b feat(butter): update DTOs for visibility, renamed Owner→UploadedBy, removed IsPublic/Owner fields
Compare 6 commits »