logidze 0.5.2 → 0.5.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: c7ac978c39954a679f81242ef85020969e2639f8
-  data.tar.gz: 1d7b280698b769ed44bda02c14249660ae67bfdd
+  metadata.gz: a553a435446577ff945a979411dcd5d36c6185e7
+  data.tar.gz: 4c06374961f3073969d5f7d16184bd7e7e8d5dd9
 SHA512:
-  metadata.gz: 22adef27322f4a653d0bcb45230261c0380476f81c6f5f11fefe09fc438fd3f1ffd1a73b52f9517b8c1b63be31ebd9802a21d63bc10e18192176e126c6df97f7
-  data.tar.gz: 0770ac7a807ff2439c54ef1d780712ad503722d7ac3e556e9de46f2096644ea8db6270bec8d17844628edce5a5c59d4613433187835e9659cdcdee3f3cb04de4
+  metadata.gz: 9bbdf6fcec9cb2e4a5686f7f80972aa43889bda5e74e7711d4e80364d580279e9f947859aa76342b3018dcf5fcc471ab6b998c5a54e9b836654dab1e94e9bdeb
+  data.tar.gz: 991804f34a2f90601794418789fde42aff8d7031a8edd6b115fb79c4e0fd59e3b14277b8931a509e19c01200d4cd830776484e6d4622059c4bca3b321d2ecfc7

data/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Change log
 
+## master
+
+## 0.5.3 (2017-08-22)
+
+- Add `--update` flag to model migration. ([@palkan][])
+
 ## 0.5.2 (2017-06-19)
 
 - Use versioned migrations in Rails 5+. ([@palkan][])

data/README.md

@@ -1,4 +1,5 @@
 [![Gem Version](https://badge.fury.io/rb/logidze.svg)](https://rubygems.org/gems/logidze) [![Build Status](https://travis-ci.org/palkan/logidze.svg?branch=master)](https://travis-ci.org/palkan/logidze) [![Circle CI](https://circleci.com/gh/palkan/logidze/tree/master.svg?style=svg)](https://circleci.com/gh/palkan/logidze/tree/master)
+[![Dependency Status](https://dependencyci.com/github/palkan/logidze/badge)](https://dependencyci.com/github/palkan/logidze)
 
 # Logidze
 
@@ -86,6 +87,12 @@ rails generate logidze:model Post --timestamp_column time
 rails generate logidze:model Post --timestamp_column nil # "null" and "false" will also work
 ```
 
+If you want to update Logidze settings for the model, run migration with `--update` flag:
+
+```ruby
+rails generate logidze:model Post --update --whitelist=title body rating
+```
+
 Logidze also supports associations versioning. It is experimental feature, and disabled by default. You can learn more
 in the [wiki](https://github.com/palkan/logidze/wiki/Associations-versioning).
 

data/lib/generators/logidze/model/USAGE

@@ -6,3 +6,8 @@ Examples:
 
     This will generate the migration to add log column and trigger.
     This will also add `has_logidze` to model.
+
+  rails generate logidze:model User --update --whitelist=name,age
+
+    This will generate the migration to update existing trigger (drop and create).
+

data/lib/generators/logidze/model/model_generator.rb

@@ -24,6 +24,9 @@ module Logidze
       class_option :timestamp_column, type: :string, optional: true,
                                       desc: "Specify timestamp column"
 
+      class_option :update, type: :boolean, optional: true,
+                            desc: "Define whether this is an update migration"
+
       def generate_migration
         if options[:blacklist] && options[:whitelist]
           $stderr.puts "Use only one: --whitelist or --blacklist"
@@ -33,6 +36,7 @@ module Logidze
       end
 
       def inject_logidze_to_model
+        return if update?
         indents = "  " * (class_name.scan("::").count + 1)
 
         inject_into_class(model_file_path, class_name.demodulize, "#{indents}has_logidze\n")
@@ -40,7 +44,11 @@ module Logidze
 
       no_tasks do
         def migration_name
-          "add_logidze_to_#{plural_table_name}"
+          if update?
+            "update_logidze_for_#{plural_table_name}"
+          else
+            "add_logidze_to_#{plural_table_name}"
+          end
         end
 
         def migration_file_name
@@ -59,6 +67,10 @@ module Logidze
           options[:only_trigger]
         end
 
+        def update?
+          options[:update]
+        end
+
         def columns_blacklist
           array = if !options[:whitelist]
                     options[:blacklist]

data/lib/generators/logidze/model/templates/migration.rb.erb

@@ -3,7 +3,9 @@ class <%= @migration_class_name %> < ActiveRecord::Migration<%= ActiveRecord::VE
   include Logidze::Migration
 
   def up
-    <% unless only_trigger? %>
+    <% if update? %>
+    execute "DROP TRIGGER logidze_on_<%= table_name %> on <%= table_name %>;"
+    <% elsif !only_trigger? %>
     add_column :<%= table_name %>, :log_data, :jsonb
     <% end %>
 
@@ -23,10 +25,19 @@ class <%= @migration_class_name %> < ActiveRecord::Migration<%= ActiveRecord::VE
   end
 
   def down
+    <% if update? %>
+    # NOTE: We have no idea on how to revert the migration
+    # ('cause we don't know the previous trigger params),
+    # but you can do that on your own.
+    # 
+    # Uncomment this line if you want to raise an error.
+    # raise ActiveRecord::IrreversibleMigration
+    <% else %>
     execute "DROP TRIGGER IF EXISTS logidze_on_<%= table_name %> on <%= table_name %>;"
 
-    <% unless only_trigger? %>
+    <% if !only_trigger? %>
     remove_column :<%= table_name %>, :log_data
     <% end %>
+    <% end %>
   end
 end

data/lib/logidze/version.rb

@@ -1,4 +1,4 @@
 # frozen_string_literal: true
 module Logidze
-  VERSION = "0.5.2"
+  VERSION = "0.5.3"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: logidze
 version: !ruby/object:Gem::Version
-  version: 0.5.2
+  version: 0.5.3
 platform: ruby
 authors:
 - palkan
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-06-19 00:00:00.000000000 Z
+date: 2017-08-22 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails
@@ -226,7 +226,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.6.4
+rubygems_version: 2.6.11
 signing_key: 
 specification_version: 4
 summary: PostgreSQL JSON-based auditing