NoFlyList : How NoFlyList Got Cleared for Production

As the maintainer of Acts-as-Taggable-On (AATO), I started seeing patterns of technical debt and maintenance challenges around 2018. While AATO served its purpose well, its legacy codebase began showing signs of strain, especially with modern Rails applications.

The Birth of NoFlyList

NoFlyList wasn't born in a weekend hackathon, it evolved over years of real-world testing across multiple production applications.

The initial concept emerged from handling complex tagging requirements in a large-scale supply chain platform, where AATO's limitations became apparent.

Let's walk through a practical example of how NoFlyList handles one of these real-world scenarios.

class Product < ApplicationRecord

  include NoFlyList::TaggableRecord



  has_tags :categories,

    polymorphic: true,           # Shared across models

    restrict_to_existing: true,  # Only allow predefined categories

    counter_cache: true         # Track usage statistics

end

This simple configuration represents years of learning about what teams actually need in production. Each option addresses specific pain points discovered in real applications:

• Polymorphic tags came from the platform needing to share categories across products and services.


• Tag restrictions emerged from a content management system requiring controlled vocabularies.


• Counter cache was added after seeing performance issues in high-traffic situations.

Database-Specific Optimizations

One feature that took significant real-world testing was the database-specific query strategies. Different applications had different scaling challenges:

# PostgreSQL-optimized query

Product.with_all_categories("electronics", "gaming")

       .with_any_features("wireless", "bluetooth")



# MySQL-specific optimizations

Product.without_any_categories("discontinued", "clearance")

Testing Infrastructure

The test helpers was build from actual testing patterns i use across multiple applications:

class ProductTest < ActiveSupport::TestCase

  include NoFlyList::TestHelper



  test "product categorization" do

    assert_taggable_record Product, :categories

    assert_tagging_context Product, :categories, polymorphic: true

  end

end

Next Steps

While NoFlyList is now ready for public use, i'm still extracting and refining features based on real-world usage patterns. Future releases will include:

• Additional query optimizations


• Enhanced migration tools


• More granular caching options

The gem is stable and production-tested, but i'm continuously identifying features that could benefit the broader Rails community.