-
-
Notifications
You must be signed in to change notification settings - Fork 142
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
V3.0.0 - Big Refactor, updated libraries, project converted to typescript, Popup refactored #270
Conversation
…Maps moved to utils
This is really awesome @Fabianurrutia! Thanks for doing all this work, so cool! Give me a few more days to look into this and give it a test, and then we can get it merged next week. |
This looks great - I have one question, that I couldn't really find the answer to online: don't we need to compile the Typescript before publishing to NPM to make it work in older RN projects? It looks like the current version of metro might support Typescript bundling of node modules out of the box, but most RN packages I could find on Github include a compilation step before publishing to NPM, I think we might need to add that as well? |
Yes, you're correct. It's generally a good practice to compile TypeScript code before publishing to npm, especially if you want to ensure compatibility with older React Native projects or environments that might not support TypeScript natively. I missed testing with previous versions, give me a couple of days and I'll do the update so it compiles correctly. |
Hi @tschoffelen It took me a little while because I wanted to install semantic-release, and test a little. I leave the example of how it would be published: https://www.npmjs.com/package/react-native-map-link-test You need to configure in the project: https://github.com/semantic-release/semantic-release/blob/master/docs/usage/ci-configuration.md In this way, every time it is updated, the publication will be automatically made based on the commits that were made. |
Made one small change to the push workflow - going to merge this now, thanks for your amazing work on this! |
🎉 This PR is included in version 3.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I noticed #282 after this update. Also, I am wondering what the reason is for removing |
Yeah, that's a fair point. We can do more to fix the default styling here. I'm happy with the move away from the separate Happy to accept styling/UX improvement PRs for the popup though! |
Fwiw I'm not sure whether only a subset of users use the popup, though; the popup has been the main use of this library for us in several projects. As of now, we need to stick to v2. PS: The change could've been better documented as well. We only caught this after upgrading, and we had to revert. |
Yep. A detailed migration guide is necessary for a major version bump with such lots of breaking changes |
Changes:
Break Changes: