Passing Authentication Method to After Authenticate Functions [HIRO-385]

[tolgatolgay]

No description provided.

[linear]

HIRO-385

[Copilot]

Pull request overview

This PR extends Hiro’s authentication-related hooks to include the authentication provider, so downstream “after authenticate” handlers and publishers can react differently based on the login method (Apple/Google/etc.).

Changes:

• Extend Publisher.Authenticate to include an AuthProvider argument.
• Extend AfterAuthenticateFn to include an AuthProvider argument.
• Introduce the AuthProvider type and constants, and update SatoriPersonalizer to match the updated publisher interface.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
publisher.go	Adds provider AuthProvider to the Publisher.Authenticate interface method.
personalizer_satori.go	Updates SatoriPersonalizer.Authenticate signature to implement the updated Publisher interface.
base.go	Adds AuthProvider type/constants and extends AfterAuthenticateFn to include the provider.

Comments suppressed due to low confidence (1)

personalizer_satori.go:246

• The new provider parameter (and created) are not used in this implementation. If they’re intentionally unused, consider renaming them to _ (or otherwise documenting why they’re unused) to avoid confusion for readers and to make it clear Satori auth does not currently depend on the auth provider.

func (p *SatoriPersonalizer) Authenticate(ctx context.Context, logger runtime.Logger, nk runtime.NakamaModule, userID string, created bool, provider AuthProvider) {
	if !p.IsPublishAuthenticateRequest() && !p.IsPublishAuthenticateRequestWithSession() {
		return
	}
	if _, err := nk.GetSatori().Authenticate(ctx, userID, nil, nil, !p.IsPublishAuthenticateRequestWithSession()); err != nil && !errors.Is(err, runtime.ErrSatoriConfigurationInvalid) {

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.