ParentRecordAccess.canReadTable passed a bare AbstractActionInput to PermissionsHelper.hasTablePermission, so the READ check did not run as an actual table read. Pass a GetInput for the table instead. Ported from the GG Forge isolated build (qbit-collaboration:0.1.0-forge.8f348daf324d-files3-recents) so Forge can pin a published 1.0.x/1.1.0 release candidate; the GG Forge test PrinterCollaborationAccessTest covers the behavior.
ParentRecordAccess.canReadTable passed a bare AbstractActionInput to PermissionsHelper.hasTablePermission, so the READ check did not run as an actual table read. Pass a GetInput for the table instead. Ported from the GG Forge isolated build (qbit-collaboration:0.1.0-forge.8f348daf324d-files3-recents) so Forge can pin a published 1.0.x/1.1.0 release candidate; the GG Forge test PrinterCollaborationAccessTest covers the behavior.
ParentRecordAccess.canReadTable passed a bare AbstractActionInput to
PermissionsHelper.hasTablePermission, so the READ check did not run as an actual
table read. Pass a GetInput for the table instead, which is what a host's table
permission rules evaluate. Ported from the GG Forge parent-read qualification.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
ParentRecordAccess.canReadTable passed a bare AbstractActionInput to PermissionsHelper.hasTablePermission, so the READ check did not run as an actual table read. Pass a GetInput for the table instead. Ported from the GG Forge isolated build (qbit-collaboration:0.1.0-forge.8f348daf324d-files3-recents) so Forge can pin a published 1.0.x/1.1.0 release candidate; the GG Forge test PrinterCollaborationAccessTest covers the behavior.