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

Fixing an issue in the order at which some configuration key are loaded #434

Merged
merged 1 commit into from
Feb 17, 2016

Conversation

mikeSimonson
Copy link
Contributor

There is validation that check that the namespace and folder name are
set. Namely the validate method in the configuration class.

Because of that check we need to make sure that the namespace is set
before any migration are loaded, as the check happen there.

There is validation that check that the namespace and folder name are
set. Namely the validate method in the configuration class.

Because of that check we need to make sure that the namespace is set
before any migration are loaded, as the check happen there.
@mikeSimonson mikeSimonson added this to the 1.3.1 milestone Feb 17, 2016
mikeSimonson added a commit that referenced this pull request Feb 17, 2016
Fixing an issue in the order at which some configuration key are loaded
@mikeSimonson mikeSimonson merged commit 60ae914 into doctrine:master Feb 17, 2016
@LogansUA
Copy link

@mikeSimonson thanks for solving this issue.

May i ask why do you add 2 key => value pair with the same key name and value for $configurationProperties array (AbstractFileConfiguration line 56)?

@mikeSimonson
Copy link
Contributor Author

@LogansUA thanks for the notice. Fixed

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

Successfully merging this pull request may close these issues.

2 participants