Way to change a service name/reference

[frapontillo]

Is there a way to change a given service name/reference through the examined source? Since AngularJS doesn't support namespacing when injecting instances and functions, I need to pre-process some libraries that conflict with each other.

Can plugins be used to achieve this?

[olov]

It's out of scope for what ng-annotate is intended to do, frankly. Plugins are not really designed for that use-case either - you need to do your processing either before or after ng-annotate runs.

I would probably have checked-in modified versions of the libraries in my repo or created a separate tool that matches [..., "foobar", ..., function(..., foobar, ...) {}] (i.e. the output of ng-annotate) and alters it accordingly. The risks of false positives would be very low. You could use https://www.npmjs.org/package/ordered-ast-traverse and https://www.npmjs.org/package/alter for simple traversal and batched text manipulations (what ng-annotate uses).

[olov]

On a second thought, perhaps this use-case should be possible to implement using plugins after all. There are some similarities to #42.

ng-annotate should mark all nodes corresponding to a parameter-injected function. Plugins should be able to register a function that runs between judgeSuspects and alter (see ng-annotate-main.js). Your plugin could then update references there.

Re-opening.

[frapontillo]

So can this be done in the following way?

1. Between judgeSuspects(ctx) and alter(src, fragments), look for fragments with a str that contains the string to replace.

   a. Replace the old string with the new one (quite naive, we should check for proper variable names here)

2. Find all of the provider definitions (controller, service, etc.)

3. Generate a defFragments array

   a. Filter the definitions with the one to replace
   b. Add the new definition fragment to the array

4. Merge defFragments with fragments

5. Proceed to alter

[olov]

Not currently, because the fragments array is not necessarily populated. Instead I'll change ng-annotate to mark all relevant nodes instead.

Similarly, I may be able to mark all definition nodes.

[frapontillo]

The function of interest is, in this case, matchRegular(node, ctx) where you check for regular definitions and return the target function. How can we save the definition fragment as well?

If we return the full node and delegate the target evaluation when building fragments, we can discriminate there against definitions and references, thus making one single pass.

EDIT: I am making some progress, I may be able to push a PR in a few, or maybe tomorrow.

[olov]

landed in 0.10