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
feat: migrate phone-input component to glimmer #745
Conversation
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.
Hey @m-jovan thanks for this, nice job 🙏
Question: is this change breaking?
Thanks for this @m-jovan, really nice! I did build and import the addon in one of our apps, and it's working like a charm 💯 |
892a16a
to
a1f925f
Compare
@dannycalleri No breaking changes were introduced with this migration. Thanks for the review! @vscav Thanks for the review as well! |
@m-jovan Since it's not a breaking change, could you add the tag |
a1f925f
to
07dfbc6
Compare
We're migrating
phone-input
component from classic Ember component to glimmer component as a prerequisite for introducing Typescript to this addon.Unfortunately we could not avoid using render modifiers since there are conflicts between using native glimmer lifecycle methods and the
intl-tel-input
lib that we are wrapping due to its manual dom manipulation of our input.Component files have been collocated to components folder in order for glimmer to be able to render properly.