Skip to main content

Accessing AngularJS from regular Javascript

I like Angular, but I hate JS. Yes, this post is about the old AngularJS.

With that out of the way...

We have a few projects that are using Razor Views from Asp.net. These are legacy projects with technical debt we just need to cope with. If you're not familiar, Razor is a templating technology which allows you to have html, javascript, templating logic and all your favorite Pokemon in one place. Sounds great right? It can suck.

So, in this project somebody came up with the idea of introducing AngularJS, and that was long before I touched the project. It was a very good idea, but it seemed a half-hearted effort and AngularJS was only used in some specific parts of the system. And I wanted more of that sweetness.


How I feel in Javascript. I never get to the light


Eventually I had to have a way to interact from my JS files with the AngularJS world. And thus this post is born for people out there that need to fight the same battle.
The scenario is very simple: if a user clicks a button which works with pure JS, some part of the application will show up, which works with AngularJS.

Obviously I tried the dumb thing of keeping the controller somewhere to be able to invoke it. But that sucks. (Lack of ) architecture is just the most obvious thing that it throws out of the window. We want to have a clean separation between the AngularJS world and the pure JS world. So the solution was this:

Have a div which has the ng-include directive. This div is declared in a Razor cshtml file.

This will include the view and will load it inside this div. The content of this view is a regular AngularJS view, but notice I am using the "as ctrl" syntax here:

The user clicks the button, and here is the handler which does all the work:

Some closing notes:
  1. I get the div that has the ng-Include directive. From here I can get the scope which is the door into the AngularJS world.
  2. I am using the $apply method. This is one of the few cases where you need to use it. If I don't use this here, the bindings might not work properly, because AngularJS has no idea that something happened. Check the docs here
  3. I am using that ctrl alias I set for my controller on the scope. Not 100% sure this is the only way you can do it, though. 

Now I have access to the load method and I can pass in parameters like I would normally do.
And all the regular magic should just work!

Comments

Post a Comment

Popular posts from this blog

The repository's repository

Ever since I started delving into architecture,  and specifically service oriented architecture, there has been one matter where opinions get divided. Let me state the problem first, and then take a look at both sides of the barricade. Given that your service layer needs to access persistent storage, how do you model that layer? It is almost common knowledge what to do here: use the Repository design pattern. So we look at the pattern and decide that it seems simple enough! Let's implement the shit out of it! Now, let's say that you will use an ORM - here comes trouble. Specifically we're using EF, but we could be talking about NHibernate or really any other. The real divisive theme is this question: should you be using the repository pattern at all when you use an ORM? I'll flat out say it: I don't think you should... except with good reason. So, sharpen your swords, pray to your gods and come with me to fight this war... or maybe stay in the couch? ...
2 comments
Read more

Follow up: improving the Result type from feedback

This post is a follow up on the previous post. It presents an approach on how to return values from a method. I got some great feedback both good and bad from other people, and with that I will present now the updated code taking that feedback into account. Here is the original: And the modified version: Following is some of the most important feedback which led to this. Make it an immutable struct This was a useful one. I can't say that I have ever found a problem with having the Result type as a class, but that is just a matter of scale. The point of this is that now we avoid allocating memory in high usage scenarios. This was a problem of scale, easily solvable. Return a tuple instead of using a dedicated Result type The initial implementation comes from a long time ago, when C# did not have (good) support for tuples and deconstruction wasn't heard of. You would have to deal with the Tuple type, which was a bit of a hassle. I feel it would complicate the ...
Post a Comment
Read more

C# 2.0 - Partial Types

For those of you interested, i found a very interesting list of features that were introduced in C# in  here . This is a very complete list that contains all the features, and i'm explaining them one by one in this post series. We've talked about  Generics  and  Iterators . Now it's time for some partial types . A partial type  is a type which definition is spread across one or more files. It doesn't have to be in multiple separated files, but can be. This is a very simple concept that can give us many benefits, let's see: If a type is partial, multiple developers can work on every part of it. This allows a more organized way of working and can lead to production improvement.  Winforms , for example, generates a partial class for the form so that the client can separately edit other parts it. This way, a part contains information about the design and the other contains the logic of the form. In fact, this is a very spread pattern across .Net. Ent...
Post a Comment
Read more