Skip to content

Commit

Permalink
in docs, move default to the end of the line for consistency
Browse files Browse the repository at this point in the history
Not sure if right after the value or at the end is better. But consistency is key.
  • Loading branch information
kbrock committed Mar 28, 2023
1 parent 9c143a2 commit 3b3edca
Showing 1 changed file with 13 additions and 12 deletions.
25 changes: 13 additions & 12 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -175,22 +175,23 @@ The `has_ancestry` method supports the following options:
:cache_depth Cache the depth of each node (See Depth Cache section)
false Do not cache depth (default)
true Cache depth in 'ancestry_depth'
String Cache depth in column referenced
String Cache depth in the column referenced
:primary_key_format regular expression that matches the format of the primary key
'[0-9]+' (default) integer ids
'[-A-Fa-f0-9]{36}' UUIDs
'[0-9]+' integer ids (default)
'[-A-Fa-f0-9]{36}' UUIDs
:touch Instruct Ancestry to touch the ancestors of a node when it changes
false (default) don't invalide nested key-based caches
false don't invalide nested key-based caches (default)
true touch all ancestors of previous and new parents
:counter_cache Whether to create counter cache column accessor.
false (default) don't store a counter cache
true store counter cache in `children_count`.
String name of column to store counter cache.
false don't store a counter cache (default)
true store counter cache in `children_count`.
String name of column to store counter cache.
:update_strategy Choose the strategy to update descendants nodes
:ruby (default) All descendants are updated using the ruby algorithm.
This triggers update callbacks for each descendant node
:sql All descendants are updated using a single SQL statement.
This strategy does not trigger update callbacks for the descendants.
This strategy is available only for PostgreSql implementations
:ruby All descendants are updated using the ruby algorithm. (default)
This triggers update callbacks for each descendant node
:sql All descendants are updated using a single SQL statement.
This strategy does not trigger update callbacks for the descendants.
This strategy is available only for PostgreSql implementations

Legacy configuration using `acts_as_tree` is still available. Ancestry defers to `acts_as_tree` if that gem is installed.

Expand Down

0 comments on commit 3b3edca

Please sign in to comment.