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

Fix #135: better GPS point validator detection of invalid coordinate numeric conversions #169

Merged
merged 5 commits into from
Feb 22, 2024

Conversation

codisart
Copy link
Contributor

@codisart codisart commented Jan 12, 2023

Q A
Bugfix yes
BC Break yes

Description

This PR is trying to fix the issue #135.
The fix is to have the string "foo" not converted to 0.0 and validated as a correct coordinate.

Copy link
Member

@Ocramius Ocramius left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please check CI failures too

src/GpsPoint.php Outdated Show resolved Hide resolved
test/GPSPointTest.php Outdated Show resolved Hide resolved
@Ocramius Ocramius added Awaiting Author Updates Bug Something isn't working labels Jan 12, 2023
@Ocramius Ocramius added this to the 2.29.1 milestone Jan 12, 2023
@Ocramius
Copy link
Member

As this is a bugfix, it should target 2.29.x

test/GPSPointTest.php Outdated Show resolved Hide resolved
@codisart codisart force-pushed the bug-135-fix-GPS-point-validator branch from 9220418 to 0675923 Compare January 12, 2023 15:23
@codisart codisart force-pushed the bug-135-fix-GPS-point-validator branch from 0675923 to 6be9176 Compare January 12, 2023 15:25
@codisart codisart changed the base branch from 2.30.x to 2.29.x January 12, 2023 15:27
@codisart codisart force-pushed the bug-135-fix-GPS-point-validator branch from 6be9176 to c0327a4 Compare January 12, 2023 15:34
@codisart codisart requested review from Ocramius and froschdesign and removed request for Ocramius and froschdesign January 13, 2023 08:23
@codisart codisart force-pushed the bug-135-fix-GPS-point-validator branch from 0063e10 to ac2b278 Compare January 31, 2023 15:41
@codisart codisart changed the base branch from 2.29.x to 2.30.x January 31, 2023 15:41
@Xerkus Xerkus removed this from the 2.29.1 milestone May 31, 2023
@codisart codisart force-pushed the bug-135-fix-GPS-point-validator branch from ac2b278 to df312bf Compare February 21, 2024 21:20
@codisart codisart changed the base branch from 2.30.x to 2.48.x February 21, 2024 21:21
@codisart codisart force-pushed the bug-135-fix-GPS-point-validator branch 2 times, most recently from a0eddb7 to 83155a0 Compare February 21, 2024 21:47
…e is_numeric function to separate cases.

Signed-off-by: codisart <[email protected]>
@codisart codisart force-pushed the bug-135-fix-GPS-point-validator branch from 83155a0 to 4923b71 Compare February 21, 2024 22:04
@Ocramius Ocramius added this to the 2.48.0 milestone Feb 22, 2024
Copy link
Member

@Ocramius Ocramius left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @codisart!

@Ocramius Ocramius changed the title Bug 135 fix gps point validator Fix #135: better GPS point validator detection of invalid coordinate numeric conversions Feb 22, 2024
@Ocramius Ocramius merged commit e77d1ca into laminas:2.48.x Feb 22, 2024
11 checks passed
@Ocramius Ocramius self-assigned this Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

GpsPoint validator needs a rewrite because it returns true for the input "foo, bar"
4 participants