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 Dec 1, 2023. It is now read-only.
I didn't see anything mentioned in the docs about this so sorry if it is already supported... Now that #728 has been resolved(which is awesome btw!) it would be nice to be able to specify a resolve property for the controller. Similar to how ui-router functions...
Without this there are only two ways to pass data into the controller that I can see. 1. attach things to the scope 2. inline the controller function so it has access to the same context as the function instantiating the modal.
I don't like #1 because we are trying to avoid attaching things $scope whenever possible. #2 is not great because it makes it ugly to test the controller. We typically put our controllers, services, etc. in their own file and require them in as needed - it would be nice to be able to test the controller in isolation.
The text was updated successfully, but these errors were encountered:
ryanray
added a commit
to zanebenefits/angular-strap
that referenced
this issue
Sep 8, 2015
I didn't see anything mentioned in the docs about this so sorry if it is already supported... Now that #728 has been resolved(which is awesome btw!) it would be nice to be able to specify a resolve property for the controller. Similar to how ui-router functions...
Without this there are only two ways to pass data into the controller that I can see. 1. attach things to the scope 2. inline the controller function so it has access to the same context as the function instantiating the modal.
I don't like #1 because we are trying to avoid attaching things $scope whenever possible. #2 is not great because it makes it ugly to test the controller. We typically put our controllers, services, etc. in their own file and require them in as needed - it would be nice to be able to test the controller in isolation.
The text was updated successfully, but these errors were encountered: