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

dev/core#1637 - Multiple fixes for Civi/Core/Paths.php #16745

Merged
merged 7 commits into from
Mar 11, 2020

Conversation

totten
Copy link
Member

@totten totten commented Mar 11, 2020

Backport of #16735 from 5.24 (RC) to 5.23 (stable).

On local WP build of this branch, the Civi-WP URLs looks correct (admin.php not admin.php/), and specifically-mentioned unit-tests (E2E/Core/* and Civi/Core/PathsTest.php) run OK.

When browsing the list of outputs from this test class, each of the test
cases was identified by its numerical position in the list of `$exs`.  This
makes it hard to keep track of the failures.

1. Add a symbolic name to each case (that's easier to search on)
2. Add more verbose output for failed assertions
The rationale will be discussed more via PR description.
The interpretation of `/.` is evolving per civicrm#16735:

* When this code was first written, it was unspecified/variable whether the value `[foo]/.` would end in `/`
* During most of the testing of 5.23.beta1, this was defined to always return `/`
* During a regression fix in 5.23.1, we're flipping it back the other way so that `[foo]/.` never ends in `/`.
Per 16735, the interpretation of `getPath('[foo]/.`)` changed
slightly - from:

* 5.22: Inconsistent/undefined tail end (may or may not have trailing `/`)
* 5.23.0: Defined to always end with `/`
* civicrm#16735: Defined to never end with `/`
@civibot
Copy link

civibot bot commented Mar 11, 2020

(Standard links)

@seamuslee001
Copy link
Contributor

Jenkins re test this please

@seamuslee001
Copy link
Contributor

Test fail unrelated

@seamuslee001 seamuslee001 merged commit eaacf65 into civicrm:5.23 Mar 11, 2020
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.

3 participants