Category Archives: angular

Home / JavaScript / angular
73 Posts

In Part 2 of my series on creating Angular templates for Visual Studio 2017, I made a relatively serviceable template for my latest Angular test. But, I knew it could improved.

More Link

The latest tooling in Visual Studio 2017 for .NET Core is pretty good. However, it seemed like built-in templates are a bit lacking. Fortunately, the dotnet sdk, and subsequently the CLI, have libraries available for various Single Page Application framework quick starts.

UPDATE – Also check out my other posts on this topic:

https://long2know.com/2017/04/net-core-angular-vs2017-templates-part-2/
https://long2know.com/2017/04/net-core-angular-vs2017-templates-part-3/

More Link

A fellow developer asked me how filter Pipes could be used for filtering based on checkboxes. Using the existing code samples I’ve created, I endeavored to put together a little demo of how this can be achieved.

More Link

Long ago, I blogged about integrated SignalR with AngularJS. An interesting behavior that I didn’t touch on was limiting messages being sent to specific clients. This is pretty easy to accomplish.

More Link

In one of my previous posts, I touched on how to build a filtered list using Angular pipes. As I’m adding more features to the table component that I’m working, I spent a little time modifying the pipe to be able to performing combinatory filtering.

More Link

One of the features that I had not implemented in my newer Angular component is sorting. Today I decided to go ahead and tackle this feature. Since the latest version of Angular is out, I’ve decided to simply refer to it as Angular. AngularJS will be used to refer to the older v1.x.

More Link

It appears that over the past few days that Angular 4.x (RTM) was released.

Interestingly, I was digging around to see if there is anything needed to edit in order to target the newer versions and found that my plunks that were targeting 2.x automagically work with and target 4.x.

One way to see this is to view the source of and you can note the version in the “ng-version” attribute that gets injected into your mark-up.

For my plunks, I immediately saw this attribute on the primary “app” component that is bootstrapped, for example:

ng-version="4.0.0"

It’s good to know that my prior plunks work as-is without modifications!

The release notes can be found here: https://angular.io/docs/ts/latest/