Skip to main content

a walk in the dark side

Previously I got my first version of simple todo rest service working with scala and play framework and had some ideas what to do next. Since then I've implemented a second version of the rest service, this time backed by MongoDB. I also managed to create a simple web application as a user interface for the service.


TL;DR;


https://github.com/jorilytter/simple-todo/tree/mongodb-integration
https://github.com/jorilytter/simple-todo-ui


MongoDB with scala


This was a idea that I had earlier and the actual implementation was pretty straightforward with the help of salat library. Integrating salat with play framework required me to implement a custom context but salat documentation already provided this solution so it was just a matter of reading the documentation.

Other issue that I faced was with reading and writing json documents but that's where play's documentation provided the needed answers after some initial searches with google.

Like before the implementation is shared at my github account https://github.com/jorilytter/simple-todo/tree/mongodb-integration.


Walking in the dark side


It's been a long time since I've done anything related to user interfaces let alone created one from the scratch. I had decided that my todo application will have a user interface and it will be done with something out of my comfort zone.

The idea had been in my head for a while. I've seen and heard how modern javascript frameworks can do pretty nice things and easily interact with rest services. I asked my colleagues what was the hip javascript framework for interacting with rest services and got to work.

The choice was AngularJS as I was told that rest integration with it would be easy to implement. Sure the implementation was easy after series of trial and error and the fact that AngularJS is evolving fast also means that Q&A found in various blogs or at stackoverflow were partly outdated even if they were just a few months old.

I don't believe my implementation follows the best practices but with my lack of expertise with javascript I'm just happy I got it working.

This is also shared at my github account https://github.com/jorilytter/simple-todo-ui. If you feel the need to comment please be gentle, as I said this is way off my comfort zone.

In the end I'm happy that I went out of my comfort zone and actually managed to get something that works and I'm definitely going to do it again.

Comments

Popular posts from this blog

Simple code: Immutability

Immutability is a special thing that in my mind deserves a short explanation and praise. If you're familiar with functional programming you surely recognice the concept of immutability because it's a key ingredient of the paradigm. In the world of object oriented programming it's not as used and as easy to use approach but there are ways to incorporate immutability to parts of the code and I strongly suggest you to do so. Quick intro to immutablity The basic idea of immutability is unchangeable data.  Lets take a example. We have a need to modify a object's property but because the object is immutable we can't just change value but instead we make a copy of the object and while making the copy we provide the new value for the copy. In code it looks something like this. val pencil = Product(name = "Pencil", category = "Office supply") val blackMarker = pencil.copy(name = "Black marker") The same idea can be applied in functions and metho

Simple code: Readability

Readability, understandability, two key incredients of great code. Easier said than done, right? What one person finds easy to read and understand another one finds incomprehensible. This is especially true when programmers have different levels of understanding on various subjects e.g. object oriented vs. functional or Node.js vs. Java. Even though there are obvious differences between paradigms and programming ecosystems there are some common conventions and ways to lower the barrier. Different approaches It's natural that in programming things happen sequentally e.g. you can have a list of objects and you need to do various things to the list like filter some values out and count a sum of the remaining objects based on some property. With the given list const stories = [   {name: "authentication", points: 43},   {name: "profile page", points: 11},   {name: "shopping cart", points: 24},   {name: "shopping history", points: 15},   {name: &qu

Simple code: Unit tests

Unit tests are the developers number one safety net. Let that sink in. This is the number one reason for writing unit tests. Unit tests are written by developers for developers to ensure that the code works as expected and handles happy and sad paths correctly. With enough unit test coverage the tests enable a safe environment for refactoring and rewriting code. Unit test scope Unit test should test a single thing, a method or function call and it should test only one use case within. In other words a unit test should test a function with a single input. This is a important guideline to understand. When a unit test tests a function with single input it makes the test isolated, repeatable and predictable. Example of good tests: @Test fun findsAddress() {   val address = findAddress("Stevens street 35", "Southport", "Australia")   assertThat(address).isNotNull() } @Test fun doesNotFindAddress() {   val address = findAddress("Stevens street 697", &q