Databases
StackOverflow2013
Postsdbo
POModules and namespace / name collision in AngularJS
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POModules and namespace / name collision in AngularJS
    primarykey
    data
    text
    <p>Consider the following jfiddle <a href="http://jsfiddle.net/bchapman26/9uUBU/29/">http://jsfiddle.net/bchapman26/9uUBU/29/</a></p> <pre><code>//angular.js example for factory vs service var app = angular.module('myApp', ['module1', 'module2']); var service1module = angular.module('module1', []); service1module.factory('myService', function() { return { sayHello: function(text) { return "Service1 says \"Hello " + text + "\""; }, sayGoodbye: function(text) { return "Service1 says \"Goodbye " + text + "\""; } }; }); var service2module = angular.module('module2', []); service2module.factory('myService', function() { return { sayHello: function(text) { return "Service2 says \"Hello " + text + "\""; }, sayGoodbye: function(text) { return "Service2 says \"Goodbye " + text + "\""; } }; }); function HelloCtrl($scope, myService) { $scope.fromService1 = myService.sayHello("World"); } function GoodbyeCtrl($scope, myService) { $scope.fromService2 = myService.sayGoodbye("World"); }​ </code></pre> <p>I have 2 modules (module1 and module2). Both module1 and module2 define a service called myService. This appears to create a name clash on myService within Angular when both modules are imported into myApp. It appears AngularJs just uses the second service definition without warning you of the possible issue.</p> <p>Very large projects (or just reusing modules in general) would have a risk of names clashing, which could be difficult to debug.</p> <p>Is there a way to prefix names with the module name so that name clashes don't happen? </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USBrian Chapman
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POModules and namespace / name collision in AngularJS
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POModules and namespace / name collision in AngularJS
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POModules and namespace / name collision in AngularJS
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAn update: I have found a possible workaround by applying a naming convention to the service names passed into the di system. See http://jsfiddle.net/bchapman26/9uUBU/32/ However, my main question still stands: Is there a native way to avoid the name clash shown above?
      singulars
      1. POModules and namespace / name collision in AngularJS
      1. USBrian Chapman
    2. COThis seems to be an problem right now, especially when you consider the potential use of 3rd party components. I have an issue raised [here](https://github.com/angular/angular.js/issues/2447).
      singulars
      1. POModules and namespace / name collision in AngularJS
      1. USBrett Postin
    3. COI would think this is not a problem (actually a feature and by design) since it is useful for testing and overriding behavior. Namespacing or using a naming convention is the way to go.
      singulars
      1. POModules and namespace / name collision in AngularJS
      1. USjhorback
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload