This post is over 2 years old. Solutions referenced in this article may no longer be valid. Please consider this when utilizing any information referenced here.
So I’ve been working on a project recently where I needed a simple predicate builder. Basically I needed a way to allow users to build a somewhat complex search using a GUI. And since we are using AngularJS on this project, here’s a quick article about how I did it.
Start with a simple AngularJS setup.
Okay, so what we’ve done so far is stub out a simple AngularJS app, with a factory that builds a Condition object. This will be the model object that we use to hold data from our predicates. We also add a starting predicate so that there’s at least one condition to search by when the user opens the page.
Now, let’s add some HTML:
So we’ve created a simple HTML stub for an AngularJS app. A couple of notes about what we’re doing here. We only show the delete button if we have more than one condition because we don’t want to get into a situation where we have no conditions. We also only show the add button on the last condition, using the magic variable $last, which is available inside the ng-repeat loop.
So if you fire this up, you should see a simple predicate already in place, because you already have one Condition object in the conditions array.
So now we need to make it do something.
Now, you should be able to add and remove conditions. Pretty neat! But how do we digest the objects we’re creating? Well, let’s do that now.
So here, the new doSearch() method we added to this scope loops through the objects and builds a searches object. You can now use this object to query whatever backend resource you would like. I feed it into $httpParamSerializer to turn it into a query string for querying an API resource. Right now, we’re just printing that to the log using console.log() so you can see what it’s doing.
So there you have it! Here’s a CodePen that demonstrates the whole thing. Enjoy!
Did something I wrote help you out?
That's great! I don't earn any money from this site - I run no ads, sell no products and participate in no affiliate programs. I do this solely because it's fun; I enjoy writing and sharing what I learn.
AngularJS’s built-in ngResource is a great tool for natively supporting REST APIs in your Angular application. But what happens when you need to support something besides a simple call that retrieves a list of JSON objects? You quickly run into the limits of ngResource. Here’s a great case where you might need to do something more complex: paging. Say you want to get a list of objects, and there’s 10,000 or so of them. You don’t want to send 10,000 objects to your frontend app. You want to send a portion of them, but you still need to indicate to the app that there are more. Surprisingly, considering how widespread this pattern is in web development, there does not seem to be a native way to accomplish this. But you can extend ngResource. Here’s how I did it.
Or, how to massively over-engineer dumping cat food into a bowl. As with many of my projects, it started with something that made me angry. In this case, it was this: The Petmate Le Bistro Pet Feeder. Okay, let’s back up a little bit. Back to about 8 or so years ago. We had a cat at the time, Pumpkin, who as objectively not a good cat. She was foul tempered on the best of days and very difficult to love. But she was my wife and I’s first pet, so we did love her all the same. She had a habit of wanting food precisely on time. And if it was late, she would raise all manner of noise until she was fed. Often this came at some ungodly early time in the morning. So I bought a Petmate Le Bistro Pet Feeder.