-
Notifications
You must be signed in to change notification settings - Fork 5
fix(OPENFRAM-007-3): CU-86akn96pf NotificationDataFetcher re-implements principal-resolution logic that CurrentPrincipalSupport already centralizes #2425
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
flamingo
wants to merge
1
commit into
main
Choose a base branch
from
ai-fix/openfram-007-3-57e732bc-9a25c19f
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🦩 🟠 NotificationDataFetcher re-implements principal-resolution logic that CurrentPrincipalSupport already centralizes
In
NotificationDataFetcher, removed the privatecurrentPrincipal()/currentRecipient()JWT-extraction methods and replaced principal acquisition with@AuthenticationPrincipal AuthPrincipalparameters on every query/mutation (matching the pattern used byPresenceDataFetcher/NotificationSettingsDataFetcher), and delegated human-user resolution to an injectedCurrentPrincipalSupport.requireHumanUserId(principal)call in the newcurrentRecipient(AuthPrincipal)helper, keeping only the AGENT/machine_id branch local since that path is specific to this fetcher. This is UNVERIFIED against the actualCurrentPrincipalSupportclass signature (I could not see its source, so the method name/parameter shaperequireHumanUserId(AuthPrincipal)is inferred from the finding text referencing "CurrentPrincipalSupport.requireHumanUserId"); if its actual signature differs (e.g., it takes no argument and resolves fromSecurityContextHolderitself, or throws a different exception, or the AGENT branch should also be delegated to it), this will fail to compile and needs adjustment to match the real API. A complete fix requires confirmingCurrentPrincipalSupport's exact method signatures fromPresenceDataFetcher/NotificationSettingsDataFetcherand aligning this file's calls and constructor injection accordingly.🤖 Prompt for AI agents
fix confidence: 🔴 35 low — review closely — react 👍/👎 to teach the reviewer