exwiw 0.4.11 → 0.5.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 23b64ea4c8b3562427b3e605fc17dec1251cf6916f2be02aeed0b3a29e03a62d
-  data.tar.gz: ce8a51a31bb84c22abd164e3ec928065dff99f1dbd6eb83c72a9520e8c7e0737
+  metadata.gz: 224bdc1d3b0f94e08463ad9e42a6e67d0592d902388b5873f5840226dbdbd3fe
+  data.tar.gz: de9ddd4a625565e0bcd28ff3f74df8da06092c443ad1f170d41c5858a24c4802
 SHA512:
-  metadata.gz: 779684b310965b1f59a7d9bb20d20d61526435845c1c3c5d7b6a6e1c7febcb96ce82d12ebf22bcb894546d8dd9f876984d302a87a2e321a1fb3aa8de8aeb4447
-  data.tar.gz: e19d3931e974e09487e6a661e482cdeac9cf665e34d80dc82ed9fff6f099ffa7cf0a2a8fec2b7f682b301899f9121f3c6fd49680fe0a70fb300bb04d7b9c9f78
+  metadata.gz: '08f564c07c09561a4b9b825bb7f6ca43a076df5b8262f165addad471639084fa5b5074330215edd36951ce0c427f510533f39d03e0632c1306ba4e9054391b33'
+  data.tar.gz: 2c161f236a676a15774fb097a7a2c4d66f95f38be8c465dfc29788b4c45165aa3b13dee2b1da771e317672e63f089d2496e10cf4fe2ebf16f97885e0e1c49c76

data/CHANGELOG.md

@@ -2,6 +2,17 @@
 
 ## [Unreleased]
 
+## [0.5.0] - 2026-06-16
+
+### Added
+
+- A YAML **config file** (`exwiw.yml`) can now hold any option except the database connection settings, so they no longer have to be repeated on every invocation. Pass it with `--config=PATH`; when `--config` is omitted, `exwiw.yml` (or `exwiw.yaml`) is loaded automatically from the current directory if present. **Options passed on the CLI take precedence** over the file (the file only fills in options not given on the CLI). Connection settings — `host`, `port`, `user`, `database`, `uri`, `password` — are **rejected** in the file (they must come from the CLI/environment); `adapter` is the one connection-related key allowed. Relative paths in the file (`schema_dir`, `output_dir`, `after_insert_hook`) are resolved relative to the config file's own directory (so a root-level `exwiw.yml` with `schema_dir: exwiw/schema` reads naturally and an absolute `--config` works from any directory). Unknown keys are rejected to catch typos, and export-only keys (`output_dir`, `output_format`, `insert_only`, `after_insert_hook`) are ignored under `explain` so one file can be shared by both subcommands.
+
+### Changed
+
+- **BREAKING**: the `export`/`explain` CLI option `--config-dir` has been renamed to `--schema-dir` to distinguish the directory of schema JSON files from the new `--config` config file. Its short form `-c` is now `--config` (the config file); `--schema-dir` has no short form. The hook contract is renamed to match: the shell-hook environment variable `EXWIW_CONFIG_DIR` is now `EXWIW_SCHEMA_DIR`, and the Ruby-hook `cli_options[:config_dir]` is now `cli_options[:schema_dir]`. Update invocations, scripts, and hooks accordingly (`--config-dir` no longer exists). `--schema-dir` is still required and has no default unless `schema_dir` is set in the config file.
+- **BREAKING**: the env var that overrides where `schema:generate`, `schema:tidy`, and `schema:generate_mongoid` write their config has been renamed from `OUTPUT_DIR_PATH` to `EXWIW_SCHEMA_DIR_PATH`, and the default output directory is now `exwiw/schema` (previously `exwiw`). The new name disambiguates it from the dump-side `--output-dir`, and the dedicated `schema/` subdirectory leaves `exwiw/` free for other artifacts (hooks, dumps). `OUTPUT_DIR_PATH` is no longer read. Existing repositories should set `EXWIW_SCHEMA_DIR_PATH` (e.g. `EXWIW_SCHEMA_DIR_PATH=exwiw` to preserve the old flat layout) and/or move their config under `exwiw/schema/`; otherwise a `generate` run will write a fresh copy into `exwiw/schema/` and leave the old files stale. The `export`/`explain` CLI is unaffected, but examples now point at `exwiw/schema`.
+
 ## [0.4.11] - 2026-06-15
 
 ### Fixed

data/README.md

@@ -72,7 +72,7 @@ exwiw \
   --port=3306 \
   --user=reader \
   --database=app_production \
-  --config-dir=exwiw \
+  --schema-dir=exwiw/schema \
   --target-table=shops \
   --ids=1 \ # comma separated ids
   --output-dir=dump \
@@ -81,7 +81,7 @@ exwiw \
 
 By default `--ids` are matched against the target table's primary key. `--ids-column=COLUMN` matches them against a different column instead (e.g. `--target-table=users --ids=alice@example.com --ids-column=email`). Related tables are still extracted correctly: their foreign keys are resolved through the target via a subquery (`WHERE fk IN (SELECT pk FROM target WHERE COLUMN IN (...))`), so only the target table's filter column changes. This is the SQL-adapter counterpart of the mongodb `--ids-field`; the two are mutually exclusive and each is rejected by the other adapter family. Note: if `COLUMN` is itself masked, re-running `delete-*` against an already-imported (masked) dump won't match, so prefer a stable natural key.
 
-When `--target-table` and `--ids` are omitted, exwiw dumps all tables defined in `--config-dir`:
+When `--target-table` and `--ids` are omitted, exwiw dumps all tables defined in `--schema-dir`:
 
 ```bash
 # dump all tables
@@ -91,7 +91,7 @@ exwiw \
   --port=5432 \
   --user=reader \
   --database=app_production \
-  --config-dir=exwiw \
+  --schema-dir=exwiw/schema \
   --output-dir=dump
 ```
 
@@ -123,25 +123,58 @@ exwiw explain \
   --adapter=postgresql \
   --host=localhost --port=5432 --user=reader \
   --database=app_production \
-  --config-dir=exwiw \
+  --schema-dir=exwiw/schema \
   --target-table=shops --ids=1
 ```
 
 The `--output-dir`, `--output-format`, `--insert-only`, and `--after-insert-hook` options are dump-specific and rejected when used with `explain`.
 
+### Config file (`exwiw.yml`)
+
+Options you would otherwise repeat on every run can be kept in a YAML config file. Pass it with `--config=PATH`; when `--config` is omitted, exwiw automatically loads `exwiw.yml` (or `exwiw.yaml`) from the current directory if present.
+
+**Options passed on the CLI always take precedence over the config file** — the config only fills in options you did not pass. This lets you commit the stable settings (which schema to read, output format, ...) while still varying the environment-specific connection details per invocation.
+
+```yaml
+# exwiw.yml — keep at the project root, alongside exwiw/schema/
+adapter: postgresql
+schema_dir: exwiw/schema
+output_dir: dump
+output_format: insert        # insert | copy
+insert_only: false
+after_insert_hook: hooks/seed.rb
+log_level: info              # debug | info
+# target_table / ids / ids_field / ids_column may also be set here
+```
+
+With the file above, only the connection details need to be supplied on the CLI:
+
+```bash
+DATABASE_PASSWORD=... exwiw \
+  --host=localhost --port=5432 --user=reader --database=app_production \
+  --target-table=shops --ids=1
+```
+
+Notes:
+
+- **Database connection settings stay on the CLI/environment.** `host`, `port`, `user`, `database`, `uri`, and `password` are **rejected** in the config file (exwiw exits with an error). `adapter` is the one connection-related key that *is* allowed in the file.
+- **Relative paths in the config (`schema_dir`, `output_dir`, `after_insert_hook`) are resolved relative to the config file's own directory**, not the current working directory. So with the config at the project root, `schema_dir: exwiw/schema` reads naturally, and an absolute `--config=/path/to/exwiw.yml` works no matter where you run from. (CLI path flags remain relative to the current directory — each source resolves relative to where it is written.) Absolute paths are used as-is.
+- Unknown keys are rejected so a typo surfaces immediately.
+- Export-only keys (`output_dir`, `output_format`, `insert_only`, `after_insert_hook`) are ignored when running `explain`, so a single config file can be shared by both subcommands.
+
 ### Generator
 
 The config generator is provided as a Rake task.
 
 ```bash
-# generate table schema under exwiw/
+# generate table schema under exwiw/schema/
 bundle exec rake exwiw:schema:generate
 ```
 
-By default, the schema files will be saved in the `exwiw` directory. You can specify a different output directory by setting the `OUTPUT_DIR_PATH` environment variable:
+By default, the schema files will be saved in the `exwiw/schema` directory. You can specify a different output directory by setting the `EXWIW_SCHEMA_DIR_PATH` environment variable:
 
 ```sh
-OUTPUT_DIR_PATH=custom_directory bundle exec rake exwiw:schema:generate
+EXWIW_SCHEMA_DIR_PATH=custom_directory bundle exec rake exwiw:schema:generate
 ```
 
 #### Tidying stale config (`schema:tidy`)
@@ -159,14 +192,14 @@ bundle exec rake exwiw:schema:tidy
 
 Because it reads the database directly, a table that still exists in the database but has lost (or never had) an ActiveRecord model is **kept** — only a table that is genuinely gone is removed. (This is the deliberate counterpart to `generate`, which is model-driven and only ever adds what the models know about.)
 
-It respects `OUTPUT_DIR_PATH` and the per-database subdirectory layout in the same way as `schema:generate`. Unlike `generate`, `tidy` never adds or regenerates entries — every surviving table/column (including hand-edited `comment` / `ignore` / `replace_with`) is left untouched, so it is safe to run on a customized config. The task prints which tables and columns it removed (or that the config was already tidy). Stale `belongs_tos` are not pruned by `tidy`; rerun `schema:generate` to refresh those.
+It respects `EXWIW_SCHEMA_DIR_PATH` and the per-database subdirectory layout in the same way as `schema:generate`. Unlike `generate`, `tidy` never adds or regenerates entries — every surviving table/column (including hand-edited `comment` / `ignore` / `replace_with`) is left untouched, so it is safe to run on a customized config. The task prints which tables and columns it removed (or that the config was already tidy). Stale `belongs_tos` are not pruned by `tidy`; rerun `schema:generate` to refresh those.
 
 #### Multiple databases
 
 If the application uses Rails' multiple-database support (`connects_to`), `schema:generate` buckets models by the database they connect to and writes each database's config files into its own subdirectory of the output directory, named after the database config name (`primary`, `analytics`, ...):
 
 ```
-exwiw/
+exwiw/schema/
   primary/
     shops.json
     users.json
@@ -267,7 +300,7 @@ This is an example of the one table schema:
 }
 ```
 
-`--config-dir` will use all json files in the specified directory.
+`--schema-dir` will use all json files in the specified directory.
 
 ### Output format
 
@@ -307,7 +340,7 @@ SQL
 
 **Shell hook**: anything other than `.rb` is exec'd as a child process. It is a pure side-effect hook — exwiw does not capture its stdout. The hook receives these env vars and inherits `DATABASE_PASSWORD` from the parent:
 
-- `EXWIW_OUTPUT_DIR`, `EXWIW_CONFIG_DIR`
+- `EXWIW_OUTPUT_DIR`, `EXWIW_SCHEMA_DIR`
 - `EXWIW_DATABASE_ADAPTER`, `EXWIW_DATABASE_HOST`, `EXWIW_DATABASE_PORT`, `EXWIW_DATABASE_USER`, `EXWIW_DATABASE_NAME`
 - `EXWIW_TARGET_TABLE`, `EXWIW_IDS` (comma-separated), `EXWIW_OUTPUT_FORMAT`
 

data/lib/exwiw/after_insert_hook.rb

@@ -31,7 +31,7 @@ module Exwiw
     def self.run_shell(path:, cli_options:, output_dir:, logger:)
       env = {
         'EXWIW_OUTPUT_DIR'       => output_dir,
-        'EXWIW_CONFIG_DIR'       => cli_options[:config_dir].to_s,
+        'EXWIW_SCHEMA_DIR'       => cli_options[:schema_dir].to_s,
         'EXWIW_DATABASE_ADAPTER' => cli_options[:database_adapter].to_s,
         'EXWIW_DATABASE_HOST'    => cli_options[:database_host].to_s,
         'EXWIW_DATABASE_PORT'    => cli_options[:database_port].to_s,

data/lib/exwiw/cli.rb

@@ -5,6 +5,7 @@ require 'optparse'
 require 'pathname'
 
 require 'json'
+require 'yaml'
 
 require 'exwiw'
 
@@ -12,6 +13,39 @@ module Exwiw
   class CLI
     KNOWN_SUBCOMMANDS = %w[export explain].freeze
 
+    # Config file loaded automatically when --config is omitted, if one exists in
+    # the current directory. Kept at the project root (rather than under exwiw/)
+    # so that config-relative paths like `schema_dir: exwiw/schema` read naturally.
+    # Both extensions are accepted; .yml wins when both are present.
+    DEFAULT_CONFIG_PATHS = %w[exwiw.yml exwiw.yaml].freeze
+
+    # Keys accepted in the config file. Anything outside this set is rejected so
+    # a typo surfaces immediately instead of being silently ignored. These mirror
+    # the non-connection CLI options (plus `adapter`).
+    ALLOWED_CONFIG_KEYS = %w[
+      adapter
+      schema_dir
+      output_dir
+      output_format
+      insert_only
+      after_insert_hook
+      log_level
+      target_table
+      target_collection
+      ids
+      ids_field
+      ids_column
+    ].freeze
+
+    # Database connection settings are environment-specific (and sometimes
+    # secret-adjacent), so they must be passed via CLI/env, never the committed
+    # config file. `adapter` is the one connection-ish key allowed in config.
+    REJECTED_CONNECTION_KEYS = %w[host port user database uri password].freeze
+
+    # Keys that only make sense for `export`. They are skipped when merging config
+    # for `explain` so a shared config file does not trip validate_explain_only!.
+    EXPORT_ONLY_CONFIG_KEYS = %w[output_dir output_format insert_only after_insert_hook].freeze
+
     def self.start(argv)
       new(argv).run
     end
@@ -34,7 +68,8 @@ module Exwiw
       @database_password = ENV["DATABASE_PASSWORD"]
       @connection_uri = nil
       @output_dir = nil
-      @config_dir = nil
+      @schema_dir = nil
+      @config_file_path = nil
       @database_adapter = nil
       @database_name = nil
       @target_table_name = nil
@@ -45,7 +80,9 @@ module Exwiw
       @output_format = nil
       @insert_only = nil
       @after_insert_hook_path = nil
-      @log_level = :info
+      # nil (not :info) so we can tell "user passed --log-level" from the default,
+      # letting a config-file value fill in; the :info default is applied later.
+      @log_level = nil
 
       parser.parse!(@argv)
     end
@@ -82,7 +119,7 @@ module Exwiw
         Runner.new(
           connection_config: connection_config,
           output_dir: @output_dir,
-          config_dir: @config_dir,
+          schema_dir: @schema_dir,
           dump_target: dump_target,
           output_format: @output_format,
           insert_only: @insert_only,
@@ -93,7 +130,7 @@ module Exwiw
       when "explain"
         ExplainRunner.new(
           connection_config: connection_config,
-          config_dir: @config_dir,
+          schema_dir: @schema_dir,
           dump_target: dump_target,
           logger: logger,
           io: $stdout,
@@ -102,6 +139,14 @@ module Exwiw
     end
 
     private def validate_options!
+      # Fill in any options not given on the CLI from the config file. Done first
+      # so a config-provided `adapter` is in place before normalization below.
+      # CLI values always win (the merge only fills nil/empty ivars).
+      apply_config_file!
+
+      # Default log level once CLI and config have both had their say.
+      @log_level ||= :info
+
       # Fold driver/Rails adapter spellings (mysql2, sqlite3) into exwiw's
       # canonical names up front, so every check below — and the
       # EXWIW_DATABASE_ADAPTER passed to hooks — sees the canonical name.
@@ -163,18 +208,18 @@ module Exwiw
         end
       end
 
-      if @config_dir.nil?
-        $stderr.puts "Config dir is required"
+      if @schema_dir.nil?
+        $stderr.puts "Schema dir is required (pass --schema-dir or set schema_dir in the config file)"
         exit 1
       end
 
-      unless Dir.exist?(@config_dir)
-        $stderr.puts "Config dir does not exist: #{@config_dir}"
+      unless Dir.exist?(@schema_dir)
+        $stderr.puts "Schema dir does not exist: #{@schema_dir}"
         exit 1
       end
 
-      if Dir.glob(File.join(@config_dir, "*.json")).empty?
-        $stderr.puts "Config dir contains no .json files: #{@config_dir}"
+      if Dir.glob(File.join(@schema_dir, "*.json")).empty?
+        $stderr.puts "Schema dir contains no .json files: #{@schema_dir}"
         exit 1
       end
 
@@ -202,6 +247,78 @@ module Exwiw
       end
     end
 
+    # Merge settings from the config file (YAML) into any options the user did
+    # not pass on the CLI. The CLI always wins: every assignment below only fills
+    # an ivar that is still nil/empty after parsing ARGV. Connection settings
+    # (except `adapter`) are rejected here — they belong on the CLI/env.
+    private def apply_config_file!
+      path =
+        if @config_file_path
+          unless File.file?(@config_file_path)
+            $stderr.puts "Config file not found: #{@config_file_path}"
+            exit 1
+          end
+          @config_file_path
+        else
+          DEFAULT_CONFIG_PATHS.map { |p| File.expand_path(p) }.find { |p| File.file?(p) }
+        end
+      return if path.nil?
+
+      # Paths inside the config file are resolved relative to the file's own
+      # directory (not cwd), so `schema_dir: exwiw/schema` reads naturally with the
+      # config kept at the project root, and an absolute --config works from any
+      # cwd. (CLI path flags stay cwd-relative — each source resolves relative to
+      # where it is written.) `path` is always absolute here.
+      base = File.dirname(path)
+
+      config = YAML.safe_load(File.read(path)) || {}
+      unless config.is_a?(Hash)
+        $stderr.puts "Config file must be a YAML mapping (key: value): #{path}"
+        exit 1
+      end
+
+      config.each_key do |key|
+        if REJECTED_CONNECTION_KEYS.include?(key)
+          $stderr.puts "'#{key}' is a database connection setting and must be passed via the CLI/environment, not the config file (#{path})"
+          exit 1
+        end
+        unless ALLOWED_CONFIG_KEYS.include?(key)
+          $stderr.puts "Unknown config key '#{key}' in #{path}. Allowed keys: #{ALLOWED_CONFIG_KEYS.join(', ')}"
+          exit 1
+        end
+      end
+
+      # For `explain`, drop export-only keys so a config shared with `export`
+      # does not make validate_explain_only! reject the run.
+      config = config.reject { |k, _| EXPORT_ONLY_CONFIG_KEYS.include?(k) } if @subcommand == "explain"
+
+      @database_adapter ||= config["adapter"]
+      @schema_dir ||= expand_dir(config["schema_dir"], base)
+      @output_dir ||= expand_dir(config["output_dir"], base)
+      @after_insert_hook_path ||= (File.expand_path(config["after_insert_hook"], base) if config["after_insert_hook"])
+      @output_format ||= config["output_format"]
+      @insert_only = config["insert_only"] if @insert_only.nil? && config.key?("insert_only")
+      @log_level ||= config["log_level"]&.to_sym
+      @target_table_name ||= config["target_table"]
+      @target_collection_name ||= config["target_collection"]
+      if @ids.empty? && config.key?("ids")
+        raw = config["ids"]
+        # Accept either a YAML list or a "1,2" string; coerce to strings to match
+        # the CLI's `--ids=1,2` -> ["1", "2"] shape.
+        @ids = (raw.is_a?(String) ? raw.split(",") : Array(raw)).map(&:to_s)
+      end
+      @ids_field ||= config["ids_field"]
+      @ids_column ||= config["ids_column"]
+    end
+
+    # Strip a trailing slash (like the CLI's dir options) and expand relative to
+    # `base` (the config file's directory). Returns nil for a nil value.
+    private def expand_dir(value, base)
+      return nil if value.nil?
+      value = value.end_with?("/") ? value[0..-2] : value
+      File.expand_path(value, base)
+    end
+
     # `--target-collection` is a mongodb-only alias of `--target-table`. Fold it
     # into @target_table_name (the single field the rest of the CLI/runner uses)
     # after rejecting the misuses: combining it with --target-table, or using it
@@ -319,7 +436,7 @@ module Exwiw
         database_user: @database_user,
         database_password: @database_password,
         output_dir: @output_dir,
-        config_dir: @config_dir,
+        schema_dir: @schema_dir,
         database_adapter: @database_adapter,
         database_name: @database_name,
         target_table: @target_table_name,
@@ -368,9 +485,12 @@ module Exwiw
           v = v.end_with?("/") ? v[0..-2] : v
           @output_dir = File.expand_path(v)
         end
-        opts.on("-c", "--config-dir=CONFIG_DIR_PATH", "Config dir path.") do |v|
+        opts.on("--schema-dir=SCHEMA_DIR_PATH", "Directory of schema JSON files. (or set schema_dir in the config file)") do |v|
           v = v.end_with?("/") ? v[0..-2] : v
-          @config_dir = File.expand_path(v)
+          @schema_dir = File.expand_path(v)
+        end
+        opts.on("-c", "--config=CONFIG_FILE_PATH", "Path to the exwiw config YAML. Defaults to ./#{DEFAULT_CONFIG_PATHS.first} (or .#{File.extname(DEFAULT_CONFIG_PATHS.last)}) when present. CLI options take precedence; paths inside the file are resolved relative to the file.") do |v|
+          @config_file_path = File.expand_path(v)
         end
         opts.on("-a", "--adapter=ADAPTER", "Database adapter: mysql, sqlite, postgresql, mongodb (aliases: mysql2, sqlite3)") { |v| @database_adapter = v }
         opts.on("--uri=URI", "Full MongoDB connection URI (mongodb:// or mongodb+srv://). mongodb adapter only; takes precedence over --host/--port/--user. TLS, replicaSet, authSource and credentials are read from the URI.") { |v| @connection_uri = v }

data/lib/exwiw/explain_runner.rb

@@ -4,13 +4,13 @@ module Exwiw
   class ExplainRunner
     def initialize(
       connection_config:,
-      config_dir:,
+      schema_dir:,
       dump_target:,
       logger:,
       io: $stdout
     )
       @connection_config = connection_config
-      @config_dir = config_dir
+      @schema_dir = schema_dir
       @dump_target = dump_target
       @logger = logger
       @io = io
@@ -53,7 +53,7 @@ module Exwiw
     end
 
     private def load_table_config(klass)
-      Dir[File.join(@config_dir, "*.json")].map do |file|
+      Dir[File.join(@schema_dir, "*.json")].map do |file|
         json = JSON.parse(File.read(file))
         klass.from(json).reject_ignored_members!
       end

data/lib/exwiw/runner.rb

@@ -7,7 +7,7 @@ module Exwiw
     def initialize(
       connection_config:,
       output_dir:,
-      config_dir:,
+      schema_dir:,
       dump_target:,
       logger:,
       output_format: 'insert',
@@ -17,7 +17,7 @@ module Exwiw
     )
       @connection_config = connection_config
       @output_dir = output_dir
-      @config_dir = config_dir
+      @schema_dir = schema_dir
       @dump_target = dump_target
       @output_format = output_format
       @insert_only = insert_only
@@ -159,7 +159,7 @@ module Exwiw
     end
 
     private def load_table_config(klass)
-      Dir[File.join(@config_dir, "*.json")].map do |file|
+      Dir[File.join(@schema_dir, "*.json")].map do |file|
         json = JSON.parse(File.read(file))
         # Drop belongs_tos/columns(fields) flagged ignore:true so they are not
         # considered during extraction. Done here (after loading from file)

data/lib/exwiw/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Exwiw
-  VERSION = "0.4.11"
+  VERSION = "0.5.0"
 end

data/lib/tasks/exwiw.rake

@@ -7,7 +7,7 @@ namespace :exwiw do
       require "exwiw"
 
       Exwiw::SchemaGenerator.from_rails_application(
-        output_dir: ENV["OUTPUT_DIR_PATH"] || "exwiw",
+        output_dir: ENV["EXWIW_SCHEMA_DIR_PATH"] || "exwiw/schema",
       ).generate!
     end
 
@@ -16,7 +16,7 @@ namespace :exwiw do
       require "exwiw"
 
       result = Exwiw::SchemaGenerator.from_rails_application(
-        output_dir: ENV["OUTPUT_DIR_PATH"] || "exwiw",
+        output_dir: ENV["EXWIW_SCHEMA_DIR_PATH"] || "exwiw/schema",
       ).tidy!
 
       if result.empty?
@@ -47,7 +47,7 @@ namespace :exwiw do
       require "exwiw"
 
       Exwiw::MongoidSchemaGenerator.from_rails_application(
-        output_dir: ENV["OUTPUT_DIR_PATH"] || "exwiw",
+        output_dir: ENV["EXWIW_SCHEMA_DIR_PATH"] || "exwiw/schema",
         skip_unsupported: ENV["EXWIW_SKIP_UNSUPPORTED"] == "1",
       ).generate!
     end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: exwiw
 version: !ruby/object:Gem::Version
-  version: 0.4.11
+  version: 0.5.0
 platform: ruby
 authors:
 - Shia