Loading, please wait.
Scaffolding all the client side models under an AngularJS application could be a laborious task. Even more laborious could become if we are to make changes to our model server side, and then have those changes be reflected client side. Now Imagine you are to have a good number of these models under a single application, moreover you are the only developer making this application a reality.
The technique exposed here is not always applicable. Nonetheless, It could be utilized in some application which could end up saving a great degree of time and heartache. In my scenario, the application utilized a NoSQL database on the back end. For most applications with this nature (NoSQL Databases such as RavenDB, MongoDB or DynamoDB) It is easy to implement what I am about to discuss.
Show-flick - The Application
Being a fan and an adopter of AngularJS myself, I was very excited when Google released Polymer. It is not that I favor an alternative to AngularJS; it is rather that I praised the efforts for a library that focus on components. I celebrated through the introduction of Polymer - when encountering that this library also have mustache binding {{}}. Incorrectly, this induce me to think that Polymer could be a flexible transition from AngularJS.
I was fast attracted by the ability to import components through a single line. No need to inject JavaScript files based on components, no need on adjusting code to make room for the new code; if the component works then it works! This was to me an exciting idea. More exciting was for me to discover that there is a community on the road of web component already on their way.
I embarked in a path of creating an application with Polymer in an attempt to dig deep into the Polymer intrinsics. Needless to say that Polymer and AngularJS are very different in nature. This post is a description of the key important features I encounter with Polymer.