This repository has been archived by the owner on Feb 6, 2020. It is now read-only.
[v3] configure() now resolves aliases defined as properties #92
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@weierophinney @Ocramius once you've recovered from the Expressive release party (congrats, Btw ;) it'd be good to get this in. Not many v2-v3 PRs involving plugin managers are going to work without it. Same goes for #91, but I'm not 100% happy with that one. |
weierophinney
added a commit
that referenced
this pull request
Feb 1, 2016
|
Cherry-picked to master for release with 3.0.3. @kynx — in the future, bugfixes can go against master; develop is for new features. Thanks for the great patches! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This supersedes #87 and fixes the problem with aliases defined in the
$aliasesproperty not being resolved.