Incorrect search-and-replace has changed "before" to "beforeQuery" and "after" with "afterQuery" during HHH-10664

Description

Commit 87e3f0fd2 from issue seems to have a search-and-replace bug that has corrupted lots of messages and comments, changing "before" into "beforeQuery" and "after" into "afterQuery", e.g.

Environment

None

Activity

Show:
Richard Bradley
April 19, 2017, 2:27 PM
Edited

I've looked at all 333 instances of "beforeQuery" individually, and all look like they should be "before" except for 7 hits, all method names similar to AbstractProducedQuery.beforeQuery()

Does that sound right?

I'll take a look at the "afterQuery" instances and create a PR.

Andrea Boriero
April 19, 2017, 2:45 PM

thanks but there is no need for a separate PR for afterQuery.

Richard Bradley
April 19, 2017, 2:59 PM

Don't worry, I'm planning a single PR for both issues.
I wanted to check the work so far.

Richard Bradley
April 19, 2017, 3:17 PM
Vlad Mihalcea
May 3, 2017, 9:27 AM

Applied PR upstream.

Assignee

Andrea Boriero

Reporter

Richard Bradley

Fix versions

Labels

None

backPortable

None

Suitable for new contributors

Yes, likely

Requires Release Note

None

backportDecision

None

Components

Affects versions

Priority

Minor
Configure