minor #60575 [Security] CleanUp UserInterface PHPDoc (Abdelhakim ABOULHAJ)

nicolas-grekas · nicolas-grekas · commit 383eede11f28 · 2025-05-30T10:33:53.000+02:00
This PR was submitted for the 7.4 branch but it was merged into the 6.4 branch instead. Discussion ---------- [Security] CleanUp UserInterface PHPDoc | Q | A | ------------- | --- | Branch? | 6.4 | Bug fix? | no | New feature? | no | Deprecations? | no | Issues | -- | License | MIT This PR removes outdated or potentially misleading references to passwords from the PHPDoc comments in the UserInterface. Since the interface does not directly handle password logic, these mentions are unnecessary and could cause confusion for implementers. **Changes**: - Removed password-related text from PHPDoc comments in UserInterface. **Reasoning**: - Clarifies the responsibilities of UserInterface. - Ensures documentation is aligned with actual interface behavior. No functional code changes have been made—this is purely a documentation cleanup. Commits ------- e51a81a doc: update UserInterface header comments
diff --git a/src/Symfony/Component/Security/Core/User/UserInterface.php b/src/Symfony/Component/Security/Core/User/UserInterface.php
@@ -15,9 +15,7 @@
  * Represents the interface that all user classes must implement.
  *
  * This interface is useful because the authentication layer can deal with
- * the object through its lifecycle, using the object to get the hashed
- * password (for checking against a submitted password), assigning roles
- * and so on.
+ * the object through its lifecycle, assigning roles and so on.
  *
  * Regardless of how your users are loaded or where they come from (a database,
  * configuration, web service, etc.), you will have a class that implements

Original file line number	Diff line number	Diff line change
`@@ -15,9 +15,7 @@`
`15`	`15`	`* Represents the interface that all user classes must implement.`
`16`	`16`	`*`
`17`	`17`	`* This interface is useful because the authentication layer can deal with`
`18`		`- * the object through its lifecycle, using the object to get the hashed`
`19`		`- * password (for checking against a submitted password), assigning roles`
`20`		`- * and so on.`
	`18`	`+ * the object through its lifecycle, assigning roles and so on.`
`21`	`19`	`*`
`22`	`20`	`* Regardless of how your users are loaded or where they come from (a database,`
`23`	`21`	`* configuration, web service, etc.), you will have a class that implements`