Bart van Zon Software developer


I'm a Vienna based software engineer with a focus on backend development using both Ruby and Elixir. With a history in promotional and telecom applications I have an expertise in scaleable applications.

For Hire

I'm available for hire on location in Vienna, Austria or remotely anywhere in Europe. More details about projects I've done in the past can be found on LinkedIn, or you can reach out to me for more info via e-mail or phone.


My main development languages are Ruby and Elixir, but I have worked with JavaScript, PHP and more.


Docker, Git, Linux, Photoshop, Vim and many more.

Rails tree structure

A couple of days ago I had to make a documents/folder structure for an app. The idea was that there’s two types of objects: categories and documents, the user can click through categories and download documents. A category can contain other categories and documents. We only had to show the category the user is currently in, the files and categories that are in that category and some way to navigate one level higher. So there was no need to see children’s children etc.

A quick search on the Ruby Toolbox shows Ancestry and a bunch of other options but most of them are way to complicated for the simple goal I was trying to achieve so I’ve decided to build it from scratch.

I started out with two models, the Category model, and the Document model.


class Category < ActiveRecord::Base
  belongs_to :parent, class_name: 'Category', foreign_key: "parent_id"
  validates :title, presence: true
  has_many :documents

  def children
    self.class.where(parent_id: id)

  def parent_title
    parent.title if parent.present?

The category can belong to other categories, and that optional parent is stored in the parent_id variable. A category has a title as we need something to show when listing the categories and a category can have several documents in it.


class Document < ActiveRecord::Base
  validates :title, presence: true
  belongs_to :category

Documents have a title to display them (and in a real world application probably a file to go with it) and it may belong to a category. If it has no category it should be displayed on the top level of the tree.


create_table "categories", force: true do |t|
  t.string   "title"
  t.integer  "parent_id"

create_table "documents", force: true do |t|
  t.string   "title"
  t.integer  "category_id"

The database schema should look something like this.

One of the problems with these models is that a category can reference to ANY category as it’s parent. So even itself, to prevent that we’ll need a custom validator, it can be added to the category model with the following line:


validates_with CategoryParentValidator

And the validator itself would look something like this:


Class CategoryParentValidator < ActiveModel::Validator
  def validate(record)
    if !record.new_record? && record.parent_id ==
      record.errors[:parent] << I18n.t('cant_be_itself', scope: 'errors.messages')

If the record is new we shouldn’t check if the parent_id is the same as the current id because the current id will be nil. So a new record without a parent would have both id’s on nil but is still valid.

The next step in building the tree structure is the controller:


class DocumentsController < ApplicationController
  before_action :set_document, only: [:show]
  before_action :set_files_variables, only: [:index, :show]

  def index

  def show

  def set_document
    @document = Document.find params[:id]

  def set_files_variables
    @selected_category = params[:selected_category]
    @parent_category = get_parent_category_id(@selected_category)
    @categories = Category.where(parent_id: @selected_category)
    @documents = Document.where(category_id: @selected_category)

  def get_parent_category_id(category_id)
      selected_category = Category.find(category_id)
      return if selected_category.parent.present?
    rescue ActiveRecord::RecordNotFound

    nil #the category was not found or there was no parent

There’s a bunch of variables we’re going to need in the view, the selected category is needed so we can show the title of the category we’re currently in. The parent_category is needed to navigate to one level higher, the categories are the categories in the selected category and the documents are the documents in the selected category.


<h3>Document List</h3>
<ul id="document_list">
  <% if @selected_category.present? %>
    <li class="parent">
    <%= link_to '..', documents_path(selected_category: @parent_category) %>
  <% end %>
<% @categories.each do |category| %>
  <li class="category">
    <%= link_to "#{category.title}", documents_path(selected_category: %>
<% end %>

<% @documents.each do |document| %>
  <li class="document <%= document_icon_class(document) %>">
    <%= link_to "#{document.title}", document_path(document, selected_category: @selected_category) %>
<% end %>

I expected the view to be pretty complex but it turned out to be easier then I expected. We show the selected category, a way of navigating and a list of categories and files in the category. Because there’s no need to see children’s children this stays pretty simple.