You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 20, 2023. It is now read-only.
The code as it sits ends up deleting a template ( because it's trying to use templateUrl )
This is because the check which is supposed to confirm existence of templateUrl is code in correctly. Specifically line 63 checkout for 'templateUrl' in settings which returns true even if the field has a value of undefined. A more appropriate check would be just settings.templateUrl which will return false in the case of undefined
The text was updated successfully, but these errors were encountered:
windbender
added a commit
to windbender/angular-confirm
that referenced
this issue
Jan 6, 2017
as a work around you can inject $confirmModalDefaults, along side $confirm, select the template, and set it on the settings object. $confirm( {text:'Confirm Delete',ok:'Yes Delete',cancel:'Cancel'} ,{template: $confirmModalDefaults.additionalTemplates['dangerTemplate'].template})
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The code as it sits ends up deleting a template ( because it's trying to use templateUrl )
This is because the check which is supposed to confirm existence of templateUrl is code in correctly. Specifically line 63 checkout for 'templateUrl' in settings which returns true even if the field has a value of undefined. A more appropriate check would be just settings.templateUrl which will return false in the case of undefined
The text was updated successfully, but these errors were encountered: