Regenerate V2 client for the unified AccessControl surface (§6.4 access rights)#61
Open
bzajzon-laserfiche wants to merge 1 commit into
Open
Regenerate V2 client for the unified AccessControl surface (§6.4 access rights)#61bzajzon-laserfiche wants to merge 1 commit into
bzajzon-laserfiche wants to merge 1 commit into
Conversation
…ss rights) Re-regen against the combined access-rights surface grouped under a single AccessControl tag: entry/field/template AccessControl + Rights, default field/template ACLs, GetSessionRights, LookupTrustees, and getTrusteeSecurity now live on a new AccessControlClient. Trustee security reshaped to getTrusteeSecurity with an includeInherited flag (TrusteeEffectiveSecurity -> TrusteeSecurity). Wire accessControlClient into IRepositoryApiClient / RepositoryApiClient (ClientBase.ts). Production baseUrl restored in swagger.json + index.ts (localhost-regen trap). Regen only — no package.json version bump (publish ships in a separate release PR).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Regenerates the V2 JS client against the combined §6.4 access-rights surface, now grouped under a single AccessControl swagger tag (server PR: site-api-repository !173579).
Changes
lf-repository-api-client-v2(index.ts+generate-client/swagger.json): entry/field/templateAccessControl+Rights, default field/template ACLs,getSessionRights,lookupTrustees, andgetTrusteeSecuritynow live on a newAccessControlClient(the formerTrusteesClientis dissolved into it).getTrusteeSecuritywith anincludeInheritedflag (effective by default, direct when false);TrusteeEffectiveSecurity→TrusteeSecurity.accessControlClientintoIRepositoryApiClient/RepositoryApiClient(ClientBase.ts).swagger.jsonservers[]andindex.tsdefaults (localhost-regen trap).Notes
package.jsonversion bump and no publish — the GA version bump + publish ship in a separate, manually-approved release PR after the server side merges.entry-access-rights(Regenerate V2 client for 6.4.A entry access-rights endpoints (REQ-ACCESS-001) #54) andfield-session-rights(Regenerate V2 client + tests for 6.4.B/C/D field/template access-rights, session rights, trustee effective security #55), now closed.