Skip to content

BUGFIX: Standalone Core - move AuthProviderFactoryInterface to correct packgage #5547

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

Open
wants to merge 2 commits into
base: 9.0
Choose a base branch
from

Conversation

mhsdesign
Copy link
Member

Neos\ContentRepository\Core MUST NOT have a dependency to Neos\ContentRepositoryRegistry

this was a hickup because at one point the cr factory did not need an AuthProviderFactoryInterface but the AuthProvider directly.

see b4e0c78

Upgrade instructions

Review instructions

Checklist

  • Code follows the PSR-2 coding style
  • Tests have been created, run and adjusted as needed
  • The PR is created against the lowest maintained branch
  • Reviewer - PR Title is brief but complete and starts with FEATURE|TASK|BUGFIX
  • Reviewer - The first section explains the change briefly for change-logs
  • Reviewer - Breaking Changes are marked with !!! and have upgrade-instructions

…ect packgage

Neos\ContentRepository\Core MUST NOT have a dependency to Neos\ContentRepositoryRegistry

this was a hickup because at one point the cr factory did not need an AuthProviderFactoryInterface but the AuthProvider directly.

see b4e0c78
reintroduced the factory at its old position and converts it to a new instance via DecoratingLegacyAuthProviderFactory

note that a manual standalone core integration via ContentRepositoryFactory will not be treated b/c because that is impossible without having the registry package installed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant