We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
v24.7.0
loadUtilsOnInit
loadUtilsOnInit: () => import('intl-tel-input/build/js/utils.js')
null
The utils script should be loaded as expected or an error should be thrown if there was an issue.
There is no error thrown in the console. When attempting to load the utils script with angular, this check fails:
intl-tel-input/src/js/intl-tel-input.ts
Line 2155 in ece711a
There was no error in the console, which made debugging this quite hard! My guess would be that this line is a bit of an overachiever:
Line 922 in ece711a
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Plugin version
v24.7.0
Steps to reproduce
loadUtilsOnInit
option in an Angular project with an import to the optionsnull
Expected behaviour
The utils script should be loaded as expected or an error should be thrown if there was an issue.
Actual behaviour
There is no error thrown in the console.
When attempting to load the utils script with angular, this check fails:
intl-tel-input/src/js/intl-tel-input.ts
Line 2155 in ece711a
My guess would be that angular patches the promise, which fails the type check and then the the utils script never gets attached to the instance.
There was no error in the console, which made debugging this quite hard! My guess would be that this line is a bit of an overachiever:
intl-tel-input/src/js/intl-tel-input.ts
Line 922 in ece711a
Thankfully someone reported a similar behaviour in #1597 that set me on the right track.
The text was updated successfully, but these errors were encountered: