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

bug fix on polyline-point #1229

Closed
wants to merge 1 commit into from

Conversation

tomokohn
Copy link

this is a suggestion to fix a bug occurring when the you update position on polyline-point

lat: changes['latitude'].currentValue,
lng: changes['longitude'].currentValue
lat: changes['latitude'] ? changes['latitude'].currentValue : null, // before this change it will fail if the there was no change in both latitude and longitude
lng: changes['longitude'] ? changes['longitude'].currentValue : null // before this change it will fail if the there was no change in both latitude and longitude
Copy link
Contributor

Choose a reason for hiding this comment

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

@tomokohn those values are checked in the if, I haven't found this issue, but I would suggest a more strong check like:
if (!!changes['latitude'] || !!changes['longitude']) {
instead of double checking those values.

Copy link
Author

Choose a reason for hiding this comment

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

this change was made after i found a bug when only one of these parameters changes.
it fix this issue : #1100

Copy link
Contributor

Choose a reason for hiding this comment

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

I see @tomokohn in that case the if is useless

Copy link

@muhammad-habib muhammad-habib left a comment

Choose a reason for hiding this comment

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

Why this PR does not be approved yet ?

@stale
Copy link

stale bot commented Dec 16, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Dec 16, 2018
@stale stale bot closed this Dec 23, 2018
@ghost ghost reopened this Jun 20, 2019
@stale stale bot removed the stale label Jun 20, 2019
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

if latitude hasn't changed, then you should upate it to the previous value, and not 'null'

@ghost
Copy link

ghost commented Jun 20, 2019

actually, my bad, I forgot this was already fixed and merged in #1597

@ghost ghost closed this Jun 20, 2019
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants