From a607c438a0a075b401ae578c495329d920492269 Mon Sep 17 00:00:00 2001 From: Duong Do Minh Chau Date: Sat, 11 May 2024 15:32:09 +0700 Subject: [PATCH] Clarify about `model_classes` in the example code --- doc/code_order.rdoc | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/code_order.rdoc b/doc/code_order.rdoc index 02902b4169..f87c774226 100644 --- a/doc/code_order.rdoc +++ b/doc/code_order.rdoc @@ -91,9 +91,11 @@ unsafe runtime modification of the configuration: model_classes.each(&:freeze) DB.freeze -The `subclasses` plugin can be used to keep track of all model classes -that have been setup in your application. Finalizing their associations -and freezing them can easily be achieved through the plugin: +`model_classes` is not a Sequel method, it indicates an array of model +classes you defined. Instead of listing them manually, the `subclasses` +plugin can be used to keep track of all model classes that have been +setup in your application. Finalizing their associations and freezing +them can easily be achieved through the plugin: # Register the plugin before setting up the models Sequel::Model.plugin :subclasses