How i discovered monkey patching while mocking aws cognito in an angular app ive been using aws cognito as the authentication piece to give users access to an angular web project im working on. Monkey patching angularjs controllers to have instance functions. Ill try to carve out some time to dig into some of this stuff soon. The module is a container for the application controllers. You then import these modules into the root module. The module itself contains the essential components for an angularjs application to function. This imho makes it easier to read whats going on with injection, differentiate between etc. If two or more componentsmodules apply monkey patch to the same. Ngzone simply forks a child zone named angular and provides callbacks in zone specifications.
The root module is all you need in a simple application with a few components. Typechecking templates in angular view engine and ivy. The module is a container for the different parts of an application. The table below lists a high level breakdown of each of the servicesfactories, filters, directives and testing components available within this core module. Although both answers are technically correct, i want to introduce a different syntax choice for this answer.
For instance the following code could trigger this error. As the app grows, you refactor the root module into feature modules that represent collections of related functionality. Monkey patching angularjs controllers to have instance functions with injectables. This error can also occur if you have tried to add your own components to the ng module. The ng module is loaded by default when an angularjs application is started. How i discovered monkey patching while mocking aws cognito.
1258 564 863 757 1509 1545 41 222 715 1251 79 1416 1294 1043 1397 1099 116 979 1534 376 827 551 1528 1413 901 1535 1371 8 203 219 327 104 1396 655 1253 1039 1486 1340 1027 989 737 617 1454 753 826