RubyFlow : The Ruby Community Blog

Home   Submit   Sign Up   Log In   leaders   Twitter   RSS Feed  

fredwu — 20 posts

If you still mostly use the truncation strategy for your tests, you might want to take a look at this blog post on how to speed up your tests. :)
It was made apparent to me that many ruby devs either aren’t aware or couldn’t be bothered to tweak their ruby garbage collector settings.

If you haven't tweaked your GC settings already, please do so now! :)
Writing good, sensible tests is hard. As a Rubyist, I feel lucky to be part of a community that embraces tests. Thought at the same time, I have come across too many projects that suffered from not having sensible tests.

So, I wrote an article to share some tips that I find useful, hopefully you too will find them useful and share some more with us. :)
I haven’t really used Sequel much therefore I am definitely a newbie. However, after days and nights of frustration, endless debugging and some search-fu, I have finally arrived at the conclusion that Sequel is a capable library, as long as you are aware of the gotchas.
Hey guys, I have just released Datamappify v0.60.0 with some revised APIs.


New API: Introduced Datamappify.config for configuring default behaviours.
API change: where now replaces find for multiple items.
API change: map_attribute now takes :to and :provider instead of a string for specifying data source.
New API: Introduced group for grouping map_attribute.
Added support for entity namespaces (closes #4).
A while ago I translated an interview with Matz done by a Chinese book publisher. The interview and the translation were well received, so this time I am translating another interview with Matz, done by Ito, the editor-in-chief from Japanese website Engineer Type.

I have put in many hours translating the text as well as doing researches to ensure the final article is readable. I hope you will enjoy it! :)

Click here to read this new interview!
I wrote a blog post about Datamappify - a gem I built for decoupling domain, persistence and form objects. :)
For those of you who don't already know, Datamappify is a library for separating domain logic from data persistence. It utilises existing ORMs so you don't lose the powerfulness of say, ActiveRecord.

Hot off the oven, we have just added nested entity composition to Datamappify! We think it's a really good way to DRY your code. We use Datamappify as a form mapper, so you may use it to compose and deal with your form data! Cool hey?

Please check out the code here:
Compose and manage domain logic and data persistence separately and intelligently, Datamappify is loosely based on the Repository Pattern and Entity Aggregation.

Datamappify is built using Virtus and existing ORMs (ActiveRecord and Sequel, etc). The design goal is to utilise the powerfulness of existing ORMs as well as to separate domain logic (model behaviour) from data persistence.

Attributes lazy loading has just been implemented, check it out:
Right now there's providers for ActiveRecord and Sequel. But imagine having support for Redis and even remote web services in the future. Domain logic just got a lot tidier. :)

Please check it out:

This is still an experimental project, I'd love to hear your thoughts!
Over the past few days I've started experimenting with the idea of implementing the repository pattern on top of ActiveRecord (yes, it sounds scary). The motivation came after we were about to kick start a relatively large scale system. It would be great to retain the powerfulness of ActiveRecord as well as making our app easier to maintain and test. It is basically a compromise, a stop gap, if you will.

I've always liked the Datamapper library but unfortunately ever since the Merb/Rails merge it has stepped outside of the spotlight. Datamapper 2 is shaping up nicely but it is still a far way away. So I decided to base my experimentation on top of utilising both ActiveRecord and Virtus, the attributes component of Datamapper 2.

You can check out what I've been doing here:

It is an experiment, and it's still too early to see how useful and practical it'll become, but I'd love to get some feedback from you guys!
A week ago I went to Shanghai, China to attend and to give a talk at RubyConf China. The day before the conference’s first day a bunch of us were invited to a VIP dinner where we met with Matz and got to play with a device running MRuby. And I heard that earlier on that day Matz was ‘adopted’ by a book publisher to do an interview.

I have found the interview (in Chinese), and found it to be really useful. So I translated it to English. Hope more people will like it. :)
I wrote this as a small practice for some ruby meta-programming fun: Ruby Decorators. The implementation is imo a little simpler than some other similar ruby decorator projects.
API Taster is useful for visually testing your Rails application's API. Version 0.5.0 has just landed with support for describing and adding metadata to API endpoints. Adding metadata is useful for say, adding response expectations so that your test suite could tap into them. :)
API Taster - A quick and easy way to visually test out your application's API.

There are already many awesome API clients (such as Postman), so why reinvent the wheel? API Taster compared to alternatives, have the following advantages:

- API endpoints are automatically generated from your Rails routes definition
- Defining post params is as easy as defining routes
- Post params can be shared with your test factories
Bustle - Activities recording and retrieving using a simple Pub/Sub architecture. The advantages:

- It is lightweight and simple to use
- It is largely self-contained and separated from you core app logic
- It works nicely with ActiveRecord out of box
- It is ORM-agnostic therefore can be extended to use with other databases
- It has full unit test coverage
Here's the repo (please read the project readme):

You are welcome to tear it apart and do whatever you want with it. :) This is probably the last time I'm going to be sucked into building something for nothing. Oh well. At least it was fun to test-drive rails 3.1. ;) Somebody buy me a beer!!!!!1 :P
Ssync was born to solve one problem - to backup/sync to Amazon S3 efficiently without too much compromises and complexity. Give it a try and see if it works out for you. :) Check out the source code here.
ActiveRecord is without doubt the de facto ORM library for Rails and many Ruby web frameworks. Many developers however, do not like database migrations and prefer to use DSL for data mapping. Datamappify is created with the sole purpose of getting rid of the DB migration headaches.

Check out the source code on Github.
Sometimes just DRY the controllers is not enough, a lot of the resources often share the same views, wouldn’t it be nice to have view files DRY’ed too? You can! Inherited Resources Views is an extremely easy to use plugin to DRY the views associated with your inherited resources controllers. It is library-agnostic (it only depends on Inherited Resources) and it supports generating both erb and haml templates. Source code available at: