Closed moovida closed 4 years ago
Thank you for this PR!
I need to review it deeper later, but here some first impressions.
I'm convinced by the InfoPoint
class. It's smarter than mine.
I'm not convinced by the name. "Info" is too vague. What about ElevatedLatLng
?
I don't understand the benefits of the changes on the notification. If I've well understood, it's just a name change.
BTW if it's really needed, it should be a second PR to split responsibilities and allow reverting if needed.
Thanks again for your interest.
I'm convinced by the InfoPoint class. It's smarter than mine.
ok, that is great.
I'm not convinced by the name. "Info" is too vague. What about ElevatedLatLng?
I chose info (even if I am also not really happy about it), because it can carry anything. But then you are right. In fact downstream apps will anyways extend the ElevatedLatLng if they add more information. I agree, most probably then your original name would be best to keep?
I don't understand the benefits of the changes on the notification. If I've well understood, it's just a name change.
Yes, I changed the name, and after the discussion above, I think it should stay as it was. The important thing is that the notification carries the complete point and not only the LatLng information.
I could redo the PR reflecting this discussion. What do you think?
Closing this pull request and opening a new one.
Just let this one open for the new ElevationPoint
, remove the notification renaming
To prevent BC we can leave the point named ElevationPoint
.
@tuarrep I had made the new pull request in order to not revert changes in this one (I am not sure that it would be so readable). Would you mind give a quick check to the other PR? I think it reflects almost everything you commented.
I would have to add as per your comments:
OK.
Closing in favor of #2
Hi @tuarrep , thanks for this amazing plugin, I love it :-)
In this pull request I would like to make a proposal to use hoverpoints that:
I hope you like the idea.