Skip to content
This repository has been archived by the owner on Jan 29, 2020. It is now read-only.

Actually use result of array_unique #44

Merged

Conversation

TysonAndre
Copy link
Contributor

This bug may have been harmless, the resulting regex built would have been
longer but functionally equivalent.

Add simple test that parsing options with duplicates
continues to succeed. (I didn't see any other tests of duplicates)

Fixes #43

Provide a narrative description of what you are trying to accomplish:

  • Are you fixing a bug?
    • Detail how the bug is invoked currently.
    • Detail the original, incorrect behavior.
    • Detail the new, expected behavior. (behavior seems to be equivalent to end users)
    • Base your feature on the master branch, and submit against that branch.
    • Add a regression test that demonstrates the bug, and proves the fix. (can't really do without accessing protected properties, which seems like a poor test)
    • Add a CHANGELOG.md entry for the fix.

This bug may have been harmless, the resulting regex would have been
equivalent.

Add simple test that parsing options with duplicates
continues to succeed. (I didn't see any other tests of duplicates)

Fixes zendframework#43
weierophinney added a commit that referenced this pull request Feb 4, 2019
weierophinney added a commit that referenced this pull request Feb 4, 2019
weierophinney added a commit that referenced this pull request Feb 4, 2019
@weierophinney
Copy link
Member

Thanks, @TysonAndre; merged to develop for release with 2.8.0.

@weierophinney weierophinney merged commit e9ed8bf into zendframework:master Feb 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

array_unique is misused in RouteMatcher->parseDefinition(), and does nothing
2 participants