Skip to content

Fix misleading docstring on require_no_authentication - #5865

Merged
carlosantoniodasilva merged 2 commits into
heartcombo:mainfrom
yottanami:agent/236-fix-require-no-authentication-comment
Oct 6, 2026
Merged

carlosantoniodasilva merged 2 commits into
heartcombo:mainfrom
yottanami:agent/236-fix-require-no-authentication-comment

Conversation

@yottanami

Copy link
Copy Markdown
Contributor

Fixes #5559.

The comment above require_no_authentication said it was for actions "where no authentication is required", which reads as "signed in or not, either is fine". The method does the opposite: it requires that the user is not signed in, and redirects a signed-in user away. This changes the comment only. The method name and behaviour are unchanged; the rename floated in the issue would break the public API, so it's left out.

Tested: bin/test on the branch, 878 runs, 2470 assertions, 0 failures, 0 errors, 0 skips.

Written with an AI coding assistant (Claude Code). The diff was reviewed and bin/test passed (878 runs, 0 failures) before submission.

yottanami and others added 2 commits September 7, 2026 20:58
The comment said 'no authentication is required', which reads as
'either state is fine'. The method actually enforces the opposite:
the user must NOT be authenticated, redirecting already-signed-in
users away. Comment-only fix; method name and behavior are unchanged.
Signed-off-by: Carlos Antonio da Silva <carlosantoniodasilva@gmail.com>
@carlosantoniodasilva
carlosantoniodasilva merged commit 52c6c55 into heartcombo:main Oct 6, 2026
22 of 60 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

require_no_authentication has an ambiguous name

2 participants