Skip to content
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

[1.3] Deprecate setDefaultRepositoryClassName and getDefaultRepositoryClassName #1840

Merged
merged 1 commit into from
Sep 5, 2018

Conversation

malarzm
Copy link
Member

@malarzm malarzm commented Aug 4, 2018

No description provided.

@malarzm malarzm added the Task label Aug 4, 2018
@malarzm malarzm added this to the 1.3.0 milestone Aug 4, 2018
{
return isset($this->attributes['defaultRepositoryClassName'])
? $this->attributes['defaultRepositoryClassName']
return isset($this->attributes['defaultDocumentRepositoryClassName'])
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This might be a tiny BC break: people May have extended this class and expect to find the attribute with the old name. Not sure if we want to deal with that, just bringing it up.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is attributes not private because we currently extended from doctrine/mongodb?

Dealing with this would likely require the new method to ensure both keys are set, but that still wouldn't guarantee they don't get out of sync by some outside forces.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is attributes not private because we currently extended from doctrine/mongodb?

Nevermind. attributes is private, so there's no issue here apart from me not being able to read properly 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants