-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Essentials] Longitude Validation #27784
Conversation
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Failing tests unrelated
🚨 API change(s) detected @davidbritch FYI |
Not sure if anything about this is described in the docs. Technically a behavioral breaking change although I think it’s for the better. |
Agreed! Devs can easily implement the previous logic and it was confusing that latitude didn't work as longitude |
while (Longitude <= -180) | ||
Longitude += 360; | ||
// check if longitude is in (-180, 180] | ||
if (Math.Abs(latitude) > 180) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kubaflo @jfversluis I feel like it's a wrong copy paste here, it should be longitude inside the Math.abs...
I guess it does describe that this area is lacking of unit tests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're absolutely right. I'm sorry about that. Here's the fix: #27834
@jfversluis could you please /azp
Issues Fixed
Fixes #27774