Skip to content
/ cool_id Public

generate ids for your rails records that have a prefix indicating what model they belong to, followed by a nanoid

License

Notifications You must be signed in to change notification settings

schpet/cool_id

Repository files navigation

cool id

gem for rails apps to generate string ids with a prefix, followed by a nanoid. similar to the ids you see in stripe's api. also able to lookup any record by id, similar to rails' globalid. there's an introductory blog post explaining why i made this.

usage

basic id generation

class User < ActiveRecord::Base
  include CoolId::Model
  cool_id prefix: "usr"
end

User.create!(name: "...").id
# => "usr_vktd1b5v84lr"

locate records

CoolId.locate("usr_vktd1b5v84lr")
# => #<User id: "usr_vktd1b5v84lr", name: "John Doe">

generate ids

e.g. for batch inserts or upserts

User.generate_cool_id
# => "usr_vktd1b5v84lr"

parsing ids

parsed = CoolId.parse("usr_vktd1b5v84lr")
# => #<struct CoolId::Id key="vktd1b5v84lr", prefix="usr", id="usr_vktd1b5v84lr", model_class=User>

parsed.model_class
# => User

configuration options

it takes parameters to change the alphabet or length

class Customer < ActiveRecord::Base
  include CoolId::Model
  cool_id prefix: "cus", alphabet: "ABCDEFGHIJKLMNOPQRSTUVWXYZ", length: 8
end

Customer.create!(name: "...").id
# => "cus_UHNYBINU"

and these can be configured globally

CoolId.configure do |config|
  config.separator = "-"
  config.alphabet = "ABCDEFGHIJKLMNOPQRSTUVWXYZ"
  config.length = 8
end

using a different id field

you can use cool_id with a separate field, keeping the default primary key:

class Product < ActiveRecord::Base
  include CoolId::Model
  cool_id prefix: "prd", id_field: :public_id
end

product = Product.create!(name: "Cool Product")
product.id  # => 1 (or a uuid or whatever primary key you like)
product.public_id  # => "prd_vktd1b5v84lr"

# locate will find this
CoolId.locate("prd_vktd1b5v84lr")  # => #<Product id: 1, public_id: "prd_vktd1b5v84lr", ...>

this approach allows you to avoid exposing your primary keys, read David Bryant Copeland's Create public-facing unique keys alongside your primary keys to learn why you might want to do this. it also allows you to adopt cool_id more easily in a project that already has some data.

installation

add cool_id to your Gemfile:

bundle add cool_id
gem "cool_id"

don't want to deal with a dependency? copy it into your project:

mkdir -p app/lib
curl https://raw.githubusercontent.com/schpet/cool_id/main/lib/cool_id.rb -o app/lib/cool_id.rb

adding cool_id to a single model

use string ids when creating a table

create_table :users, id: :string do |t|
  t.string :name
end

include the CoolId::Model concern in the active record model and set up a prefix

class User < ActiveRecord::Base
  include CoolId::Model
  cool_id prefix: "usr"
end

note: if you prefer more traditional primary keys (like bigints or uuids) you can use the id_field on a different column.

using cool_id on all models

you have drank the coolaid. setup rails to use string ids on all new generated migrations

# config/initializers/generators.rb
Rails.application.config.generators do |g|
  g.orm :active_record, primary_key_type: :string
end

then setup ApplicationRecord to include cool id and ensure it's setup in classes that inherit from it

# app/models/application_record.rb
class ApplicationRecord < ActiveRecord::Base
  include CoolId::Model
  primary_abstract_class
  enforce_cool_id_for_descendants
end

graphql

if you use the graphql ruby node interface, you can implement object identification

# app/graphql/app_schema.rb
class AppSchema < GraphQL::Schema
  def self.id_from_object(object, type_definition, query_ctx)
    object.id
  end

  def self.object_from_id(id, query_ctx)
    CoolId.locate(id)
  end
end

About

generate ids for your rails records that have a prefix indicating what model they belong to, followed by a nanoid

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published