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

v2.0 🎉 🎉 🎉 #130

Open
wants to merge 23 commits into
base: master
Choose a base branch
from
Open

v2.0 🎉 🎉 🎉 #130

wants to merge 23 commits into from

Conversation

AnatoleLucet
Copy link
Collaborator

No description provided.

@AnatoleLucet AnatoleLucet marked this pull request as draft June 13, 2023 17:40
package.json Outdated Show resolved Hide resolved
@MicheleBertoli
Copy link
Owner

Awesome stuff, well done @AnatoleLucet
I left a few comments, please let me know if they make sense

I also have a couple of questions:

  • could you please add the instructions to install/run the package and the examples?
  • I see that there's no tests right now, may I ask what's the plan?

@AnatoleLucet
Copy link
Collaborator Author

Thanks for taking the time to review this whole pr 🙏

could you please add the instructions to install/run the package and the examples?

Yes, I'm planning on writing the doc in the readme and make a contributing.md file.

I see that there's no tests right now, may I ask what's the plan?

I was planning on writing tests cases mainly for the lib/ folder and maybe a few for components/ and hooks/.
Since components/ and hooks/ are tightly coupled with google-maps, it might be a bit complicated to write complete tests suits for them. I'll see what's possible, but if you have any advice, I'm more than interested!

@AnatoleLucet AnatoleLucet force-pushed the feat/v2.0 branch 5 times, most recently from 24e22cc to c0e80d3 Compare June 27, 2023 08:18
.env.dist Outdated Show resolved Hide resolved
.env.dist Outdated Show resolved Hide resolved
@MicheleBertoli
Copy link
Owner

Hello @AnatoleLucet, and thanks once again for the outstanding work on the v2.
I love the simplicity and intuitiveness of the API, the docs, and the examples so much :)

I spent some time reviewing the PR and left a few comments - please let me know if they make sense.

Happy to merge and ship under next (and explore a testing strategy in parallel).

@MicheleBertoli
Copy link
Owner

npm install react-gmaps@next 🚀🚀🚀

@MicheleBertoli
Copy link
Owner

It seems there's a little formatting issue on examples/basic/pnpm-lock.yaml
Do we want to fix it before merging? (just to get all the lights green :))

Thanks once again for the excellent work, feel free to merge into master in your own time.

@MicheleBertoli
Copy link
Owner

FYI I'm playing around with Cypress (running the marker example and checking that the marker is there)

Screenshot 2023-09-09 at 11 00 51

@AnatoleLucet
Copy link
Collaborator Author

Hey @MicheleBertoli
Amazing! Thanks for releasing the new version! 🎉 🎉

I fixed the CI and pushed a few small changes. I think you need to approve the PR for me to be able to merge it, but feel free to merge!

MicheleBertoli
MicheleBertoli previously approved these changes Sep 16, 2023
Copy link
Owner

@MicheleBertoli MicheleBertoli left a comment

Choose a reason for hiding this comment

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

🙌

const map = useGMapsInstance();
const google = useGMapsSDK();

const polyline = React.useRef<google.maps.Polygon | null>(null);
Copy link
Owner

Choose a reason for hiding this comment

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

I just notice this - I believe it should be const polygon.

@MicheleBertoli MicheleBertoli dismissed their stale review September 17, 2023 17:18

Double-check that events are working

@MicheleBertoli
Copy link
Owner

@AnatoleLucet, sorry for putting this back in your queue.

However, as I was working on e2e tests, I noticed that events don't seem to be working.
Repro: add onClick={() => console.log("clicked")} to GMapsMarker in marker example.

From a quick look, it seems the issue is that the hook that adds the event listeners only runs on updates.
In fact, it works when the component re-renders.

I hope this makes sense, and happy to provide more context if valuable.

@AnatoleLucet
Copy link
Collaborator Author

Interesting. Good thing we're going to have test cases for this then 😅
Thanks for the feedback, i'll check as soon as possible 🙏

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.

None yet

2 participants