expressir 2.1.21 → 2.1.23

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5523a9cdb1e5b8168a0d2d7262cdd8a5e849b066a3eeaaad90a3bcb3a640fe38
-  data.tar.gz: 293acbebeecc50a22ba8bc56aa8413f7e156dac17fa4fa872380aff5a9bf320c
+  metadata.gz: b862b81010dd9fcdfe17e323db319206a7cae0ee23bbc2f5fa67f2425902c45f
+  data.tar.gz: 1e18551038a0e7a0577e7017ca6404c6e0a6424473b969f2ed8d18469ee516fb
 SHA512:
-  metadata.gz: b756fab7be254dc71ab78ce9ffdb220c727cc1ef8599c2e293ee2edb35d8fb7f2ab9e127683e7621d5a0ac2df4379efa5ff1c2aeaa8dd7623b94b18d5e778d7e
-  data.tar.gz: cb767afb4bef0a7555b9519a29b1cefa14ba3c96278d5154e2c2b5af29e813ba0824ffb7efbfd2e601f2e606f0a5800595b8a97b7998a83dd80c4d99448e7546
+  metadata.gz: eb30354610152c62957729f35389ce727a58e1867701bd22728333459ff291851befa809ba3c7165d6da658a85a31f88603d7a48492c1a6bd5845b2a6df10c68
+  data.tar.gz: eb5a9690942e44db8fd304c77efa967e57919b2b5b25149b65abb3c870b6adb5667b94fa8e87ec3d78aab59a5dbf1006350054e5728fbe17e8372a196444bc26

data/.rubocop.yml

@@ -1,14 +1,14 @@
-require:
-  - rubocop-performance
-
 inherit_from:
   - https://raw.githubusercontent.com/riboseinc/oss-guides/master/ci/rubocop.yml
   - .rubocop_todo.yml
 
-Naming/VariableName:
-  Exclude:
-  - lib/expressir/express/visitor.rb
-Layout/LineLength:
-  Max: 160
+plugins:
+- rubocop-performance
+- rubocop-rake
+- rubocop-rspec
+
 AllCops:
-  TargetRubyVersion: 2.7
+  TargetRubyVersion: 3.0
+  NewCops: enable
+  Exclude:
+    - 'vendor/**/*'

data/.rubocop_todo.yml

@@ -1,25 +1,17 @@
 # This configuration was generated by
 # `rubocop --auto-gen-config`
-# on 2025-06-07 05:08:55 UTC using RuboCop version 1.75.2.
+# on 2025-07-04 10:39:56 UTC using RuboCop version 1.77.0.
 # The point is for the user to remove these configuration records
 # one by one as the offenses are removed from the code base.
 # Note that changes in the inspected code, or installation of new
 # versions of RuboCop, may require this file to be generated again.
 
-# Offense count: 1
-# Configuration parameters: Severity, Include.
-# Include: **/*.gemspec
-Gemspec/RequiredRubyVersion:
-  Exclude:
-    - 'expressir.gemspec'
-
-# Offense count: 2
+# Offense count: 550
 # This cop supports safe autocorrection (--autocorrect).
-# Configuration parameters: Max, AllowHeredoc, AllowURI, URISchemes, IgnoreCopDirectives, AllowedPatterns, SplitStrings.
+# Configuration parameters: Max, AllowHeredoc, AllowURI, AllowQualifiedName, URISchemes, IgnoreCopDirectives, AllowedPatterns, SplitStrings.
 # URISchemes: http, https
 Layout/LineLength:
-  Exclude:
-    - 'lib/expressir/express/parser.rb'
+  Enabled: false
 
 # Offense count: 1
 # Configuration parameters: IgnoreLiteralBranches, IgnoreConstantBranches, IgnoreDuplicateElseBranch.
@@ -27,25 +19,6 @@ Lint/DuplicateBranch:
   Exclude:
     - 'lib/expressir/coverage.rb'
 
-# Offense count: 1
-# This cop supports safe autocorrection (--autocorrect).
-Lint/ScriptPermission:
-  Exclude:
-    - 'update_yaml_fixtures.rb'
-
-# Offense count: 3
-Lint/ShadowingOuterLocalVariable:
-  Exclude:
-    - 'lib/expressir/express/visitor.rb'
-
-# Offense count: 2
-# This cop supports safe autocorrection (--autocorrect).
-# Configuration parameters: AutoCorrect, IgnoreEmptyBlocks, AllowUnusedKeywordArguments.
-Lint/UnusedBlockArgument:
-  Exclude:
-    - 'lib/expressir/express/visitor.rb'
-    - 'spec/support/yaml_matchers.rb'
-
 # Offense count: 2
 # This cop supports safe autocorrection (--autocorrect).
 # Configuration parameters: AutoCorrect, AllowUnusedKeywordArguments, IgnoreEmptyMethods, IgnoreNotImplementedMethods, NotImplementedExceptions.
@@ -55,7 +28,7 @@ Lint/UnusedMethodArgument:
     - 'lib/expressir/express/cache.rb'
     - 'lib/expressir/express/parser.rb'
 
-# Offense count: 76
+# Offense count: 79
 # Configuration parameters: AllowedMethods, AllowedPatterns, CountRepeatedAttributes, Max.
 Metrics/AbcSize:
   Exclude:
@@ -74,11 +47,11 @@ Metrics/AbcSize:
     - 'lib/expressir/model/declarations/schema.rb'
     - 'lib/expressir/model/model_element.rb'
 
-# Offense count: 2
-# Configuration parameters: CountComments, CountAsOne, AllowedMethods, AllowedPatterns.
+# Offense count: 1
+# Configuration parameters: CountComments, CountAsOne, AllowedMethods, AllowedPatterns, inherit_mode.
 # AllowedMethods: refine
 Metrics/BlockLength:
-  Max: 143
+  Max: 46
 
 # Offense count: 56
 # Configuration parameters: AllowedMethods, AllowedPatterns, Max.
@@ -95,10 +68,10 @@ Metrics/CyclomaticComplexity:
     - 'lib/expressir/model/model_element.rb'
     - 'spec/support/model_element_helper.rb'
 
-# Offense count: 100
+# Offense count: 105
 # Configuration parameters: CountComments, CountAsOne, AllowedMethods, AllowedPatterns.
 Metrics/MethodLength:
-  Max: 82
+  Max: 106
 
 # Offense count: 44
 # Configuration parameters: AllowedMethods, AllowedPatterns, Max.
@@ -112,29 +85,68 @@ Metrics/PerceivedComplexity:
     - 'lib/expressir/model/declarations/schema.rb'
     - 'lib/expressir/model/model_element.rb'
 
-# Offense count: 1
-# Configuration parameters: NamePrefix, ForbiddenPrefixes, AllowedMethods, MethodDefinitionMacros, UseSorbetSigs.
-# NamePrefix: is_, has_, have_, does_
-# ForbiddenPrefixes: is_, has_, have_, does_
-# AllowedMethods: is_a?
-# MethodDefinitionMacros: define_method, define_singleton_method
-Naming/PredicateName:
+# Offense count: 135
+# Configuration parameters: EnforcedStyle, AllowedIdentifiers, AllowedPatterns, ForbiddenIdentifiers, ForbiddenPatterns.
+# SupportedStyles: snake_case, camelCase
+Naming/VariableName:
   Exclude:
-    - 'spec/**/*'
-    - 'lib/expressir/coverage.rb'
+    - 'lib/expressir/express/visitor.rb'
 
 # Offense count: 5
 Performance/FixedSize:
   Exclude:
     - 'lib/expressir/express/formatter.rb'
 
+# Offense count: 6
+Performance/MapMethodChain:
+  Exclude:
+    - 'lib/expressir/commands/coverage.rb'
+    - 'spec/expressir/commands/coverage_ignore_files_spec.rb'
+    - 'spec/expressir/coverage_spec.rb'
+
+# Offense count: 102
+# Configuration parameters: CountAsOne.
+RSpec/ExampleLength:
+  Max: 123
+
+# Offense count: 14
+# Configuration parameters: Max, AllowedIdentifiers, AllowedPatterns.
+RSpec/IndexedLet:
+  Exclude:
+    - 'spec/expressir/model/data_types/array_spec.rb'
+    - 'spec/expressir/model/data_types/bag_spec.rb'
+    - 'spec/expressir/model/data_types/binary_spec.rb'
+    - 'spec/expressir/model/data_types/real_spec.rb'
+    - 'spec/expressir/model/data_types/set_spec.rb'
+    - 'spec/expressir/model/data_types/string_spec.rb'
+
 # Offense count: 1
-Style/MissingRespondToMissing:
+RSpec/IteratedExpectation:
   Exclude:
-    - 'lib/expressir/express/visitor.rb'
+    - 'spec/expressir/schema_manifest_spec.rb'
+
+# Offense count: 235
+RSpec/MultipleExpectations:
+  Max: 114
+
+# Offense count: 21
+# Configuration parameters: AllowSubject.
+RSpec/MultipleMemoizedHelpers:
+  Max: 13
+
+# Offense count: 5
+RSpec/PendingWithoutReason:
+  Exclude:
+    - 'spec/expressir/model/declarations/remark_item_spec.rb'
+    - 'spec/expressir/model/declarations/rule_spec.rb'
+    - 'spec/expressir/model/declarations/schema_spec.rb'
 
 # Offense count: 2
-# This cop supports unsafe autocorrection (--autocorrect-all).
-Style/SlicingWithRange:
+RSpec/RepeatedExample:
+  Exclude:
+    - 'spec/expressir/model/data_types/logical_spec.rb'
+
+# Offense count: 1
+Style/MissingRespondToMissing:
   Exclude:
     - 'lib/expressir/express/visitor.rb'

data/Gemfile

@@ -10,6 +10,6 @@ gem "rake"
 gem "rspec"
 gem "rubocop"
 gem "rubocop-performance"
-gem "rubocop-rake", require: false
-gem "rubocop-rspec", require: false
+gem "rubocop-rake"
+gem "rubocop-rspec"
 gem "yard"

data/README.adoc

@@ -178,17 +178,17 @@ expressir benchmark schemas/resources/action_schema/action_schema.exp --ips
 expressir benchmark schemas/resources/action_schema/action_schema.exp --format json
 ----
 
-==== Benchmark multiple files from YAML
+==== Benchmark multiple files from schema manifest
 
-Create a YAML file with a list of schema paths:
+Create a schema manifest YAML file with a list of schema paths:
 
 .schemas.yml
 [source, yaml]
 ----
 schemas:
-  - schemas/resources/action_schema/action_schema.exp
-  - schemas/resources/approval_schema/approval_schema.exp
-  - schemas/resources/date_time_schema/date_time_schema.exp
+  - path: schemas/resources/action_schema/action_schema.exp
+  - path: schemas/resources/approval_schema/approval_schema.exp
+  - path: schemas/resources/date_time_schema/date_time_schema.exp
 ----
 
 Then benchmark all schemas at once:
@@ -271,6 +271,7 @@ The coverage command supports different output formats and exclusion options:
 | `--format json` | Output in JSON format for programmatic processing
 | `--format yaml` | Output in YAML format for programmatic processing
 | `--exclude TYPES` | Comma-separated list of EXPRESS entity types to exclude from coverage analysis
+| `--ignore-files PATH` | Path to YAML file containing array of files to ignore from overall coverage calculation
 |===
 
 ==== Excluding entity types from coverage
@@ -360,11 +361,12 @@ expressir coverage --exclude=TYPE:SELECT,FUNCTION:INNER schemas/resources/action
 
 This is useful when you want to focus documentation coverage on top-level
 functions while excluding nested helper functions that may not require
-individual documentation.
+individual documentation. The exclusion works recursively, excluding functions
+at any nesting level within other constructs.
 
 Valid FUNCTION subtypes that can be excluded:
 
-`INNER`:: Inner functions nested within other functions, rules, or procedures
+`INNER`:: Inner functions nested within other functions, rules, or procedures (at any depth)
 +
 [example]
 ====
@@ -372,14 +374,172 @@ Valid FUNCTION subtypes that can be excluded:
 FUNCTION outer_function : BOOLEAN;
   -- This inner function would be excluded with FUNCTION:INNER
   FUNCTION inner_helper_function : BOOLEAN;
+    -- Even deeply nested functions are excluded
+    FUNCTION deeply_nested_function : BOOLEAN;
+      RETURN (TRUE);
+    END_FUNCTION;
     RETURN (TRUE);
   END_FUNCTION;
 
   RETURN (TRUE);
 END_FUNCTION;
+
+RULE example_rule FOR (some_entity);
+  -- Inner functions in rules are also excluded
+  FUNCTION inner_function_in_rule : BOOLEAN;
+    RETURN (TRUE);
+  END_FUNCTION;
+WHERE
+  WR1: inner_function_in_rule();
+END_RULE;
+
+PROCEDURE example_procedure;
+  -- Inner functions in procedures are also excluded
+  FUNCTION inner_function_in_procedure : BOOLEAN;
+    RETURN (TRUE);
+  END_FUNCTION;
+END_PROCEDURE;
 ----
 ====
 
+The `FUNCTION:INNER` exclusion helps maintain focus on documenting the primary
+API functions while ignoring implementation details of nested helper functions.
+
+==== Ignoring files from coverage calculation
+
+You can exclude entire files from the overall coverage calculation using the
+`--ignore-files` option. This is useful when you have files that should not
+contribute to the overall documentation coverage statistics, such as test
+schemas, example files, or legacy schemas.
+
+[source, sh]
+----
+# Use ignore files to exclude specific files from coverage calculation
+expressir coverage --ignore-files ignore_list.yaml schemas/resources/
+
+# Combine with other options
+expressir coverage --ignore-files ignore_list.yaml --exclude=TYPE:SELECT --format=json schemas/resources/
+----
+
+===== Ignore files YAML format
+
+The ignore files YAML should contain an array of file patterns. Each pattern
+can be either an exact file path or use glob patterns for matching multiple files.
+
+.ignore_list.yaml
+[source, yaml]
+----
+# Array of file patterns to ignore
+- examples/test_schema.exp                    # Exact file path
+- examples/*_test_*.exp                       # Glob pattern for test files
+- legacy/old_*.exp                           # Glob pattern for legacy files
+- temp/temporary_schema.exp                   # Another exact path
+----
+
+===== Pattern matching behavior
+
+File patterns in the ignore files YAML support:
+
+* **Exact paths**: Match specific files exactly
+* **Glob patterns**: Use `*` for wildcard matching
+* **Relative paths**: Patterns are resolved relative to the YAML file's directory
+* **Absolute paths**: Full system paths are also supported
+
+[source, yaml]
+----
+# Examples of different pattern types
+- schemas/action_schema/action_schema.exp     # Exact relative path
+- /full/path/to/schema.exp                   # Absolute path
+- schemas/**/test_*.exp                      # Recursive glob pattern
+- temp/*.exp                                 # All .exp files in temp directory
+----
+
+===== Behavior of ignored files
+
+When files are ignored using the `--ignore-files` option:
+
+. **Excluded from overall statistics**: Ignored files do not contribute to the
+   overall coverage percentage calculation
+
+. **Still processed and reported**: Ignored files are still analyzed and appear
+   in the output, but marked with an `ignored: true` flag
+
+. **Separate reporting section**: In JSON/YAML output formats, ignored files
+   appear in both the main `files` section (with the ignored flag) and in a
+   separate `ignored_files` section
+
+. **Overall statistics updated**: The overall statistics include additional
+   fields showing the count of ignored files and entities
+
+.Example JSON output with ignored files:
+[source, json]
+----
+{
+  "overall": {
+    "coverage_percentage": 75.0,
+    "total_entities": 100,
+    "documented_entities": 75,
+    "undocumented_entities": 25,
+    "ignored_files_count": 2,
+    "ignored_entities_count": 15
+  },
+  "files": [
+    {
+      "file": "schemas/main_schema.exp",
+      "ignored": false,
+      "coverage": 80.0,
+      "total": 50,
+      "documented": 40,
+      "undocumented": ["entity1", "entity2"]
+    },
+    {
+      "file": "examples/test_schema.exp",
+      "ignored": true,
+      "matched_pattern": "examples/*_test_*.exp",
+      "coverage": 20.0,
+      "total": 10,
+      "documented": 2,
+      "undocumented": ["test_entity1", "test_entity2"]
+    }
+  ],
+  "ignored_files": [
+    {
+      "file": "examples/test_schema.exp",
+      "matched_pattern": "examples/*_test_*.exp",
+      "coverage": 20.0,
+      "total": 10,
+      "documented": 2,
+      "undocumented": ["test_entity1", "test_entity2"]
+    }
+  ]
+}
+----
+
+===== Error handling
+
+The ignore files functionality handles various error conditions gracefully:
+
+* **Missing YAML file**: If the specified ignore files YAML doesn't exist, a
+  warning is displayed and coverage analysis continues normally
+
+* **Invalid YAML format**: If the YAML file is malformed or doesn't contain an
+  array, a warning is displayed and the file is ignored
+
+* **Non-matching patterns**: Patterns that don't match any files are silently
+  ignored (no error or warning)
+
+* **Permission errors**: File access errors are reported as warnings
+
+===== Use cases for ignore files
+
+Common scenarios where ignore files are useful:
+
+* **Test schemas**: Exclude test or example schemas from production coverage metrics
+* **Legacy files**: Ignore old schemas that are being phased out
+* **Generated files**: Exclude automatically generated schemas
+* **Work-in-progress**: Temporarily ignore files under development
+* **Different coverage standards**: Apply different documentation standards to different file sets
+
 Valid TYPE subtypes that can be excluded:
 
 `AGGREGATE`:: Aggregate type
@@ -705,6 +865,203 @@ all_entities = Expressir::Coverage.find_entities(schema)
 puts "Found #{all_entities.size} entities in schema #{schema.id}"
 ----
 
+=== EXPRESS schema manifest
+
+==== General
+
+The EXPRESS schema manifest is a file format defined by ELF at
+https://www.expresslang.org/docs[EXPRESS schema manifest specification].
+
+Expressir provides a `SchemaManifest` class for managing collections of EXPRESS
+schema files. This is particularly useful when working with multiple related
+schemas or when you need to organize schema files in a structured way.
+
+The `SchemaManifest` class allows you to:
+
+* Load schema file lists from YAML manifest files
+* Manage schema metadata and paths
+* Programmatically create and manipulate schema collections
+* Save manifest configurations to files
+
+
+[example]
+.Example project structure with schema manifest:
+====
+[source]
+----
+project/
+├── schemas.yml   # Schema manifest
+└── schemas/
+    ├── core/
+    │   ├── action_schema.exp
+    │   └── approval_schema.exp
+    └── extensions/
+        └── date_time_schema.exp
+----
+
+.schemas.yml
+[source,yaml]
+----
+schemas:
+  - path: schemas/core/action_schema.exp
+    id: action_schema
+  - path: schemas/core/approval_schema.exp
+    id: approval_schema
+  - path: schemas/extensions/date_time_schema.exp
+    id: date_time_schema
+----
+====
+
+==== Creating a schema manifest
+
+===== From a YAML file
+
+Load an existing schema manifest from a YAML file:
+
+[source,ruby]
+----
+# Load manifest from file
+manifest = Expressir::SchemaManifest.from_file("schemas.yml")
+
+# Access schema entries
+manifest.schemas.each do |schema_entry|
+  puts "Schema path: #{schema_entry.path}"
+  puts "Schema ID: #{schema_entry.id}" if schema_entry.id
+end
+
+# Get all schema file paths
+schema_paths = manifest.schemas.map(&:path)
+----
+
+===== Programmatically
+
+Create a new schema manifest programmatically:
+
+[source,ruby]
+----
+# Create an empty manifest
+manifest = Expressir::SchemaManifest.new
+
+# Add schema entries
+manifest.schemas << Expressir::SchemaManifestEntry.new(
+  path: "schemas/action_schema.exp",
+  id: "action_schema"
+)
+
+manifest.schemas << Expressir::SchemaManifestEntry.new(
+  path: "schemas/approval_schema.exp"
+)
+
+# Set base path for the manifest
+manifest.base_path = "/path/to/schemas"
+----
+
+==== Schema manifest YAML format
+
+The schema manifest uses a structured YAML format:
+
+[source,yaml]
+----
+schemas:
+  - path: schemas/resources/action_schema/action_schema.exp
+    id: action_schema
+  - path: schemas/resources/approval_schema/approval_schema.exp
+    id: approval_schema
+  - path: schemas/resources/date_time_schema/date_time_schema.exp
+----
+
+===== Schema entry attributes
+
+Each schema entry in the manifest can have the following attributes:
+
+`path`:: (Required) The file path to the EXPRESS schema file
+`id`:: (Optional) A unique identifier for the schema
+`container_path`:: (Optional) Container path information
+
+
+==== Working with schema manifests
+
+===== Saving manifests
+
+Save a manifest to a file:
+
+[source,ruby]
+----
+# Save to a specific file
+manifest.to_file("output_schemas.yml")
+
+# Save to a path with automatic filename
+manifest.save_to_path("/path/to/output/")
+----
+
+===== Concatenating manifests
+
+Combine multiple manifests:
+
+[source,ruby]
+----
+manifest1 = Expressir::SchemaManifest.from_file("schemas1.yml")
+manifest2 = Expressir::SchemaManifest.from_file("schemas2.yml")
+
+# Concatenate manifests
+combined_manifest = manifest1.concat(manifest2)
+
+# Or use the + operator
+combined_manifest = manifest1 + manifest2
+----
+
+===== Using manifests with parsers
+
+Parse all schemas from a manifest:
+
+[source,ruby]
+----
+# Load manifest
+manifest = Expressir::SchemaManifest.from_file("schemas.yml")
+
+# Get schema file paths
+schema_paths = manifest.schemas.map(&:path)
+
+# Parse all schemas
+repository = Expressir::Express::Parser.from_files(schema_paths)
+
+# With progress tracking
+repository = Expressir::Express::Parser.from_files(schema_paths) do |filename, schemas, error|
+  if error
+    puts "Error loading #{filename}: #{error.message}"
+  else
+    puts "Successfully loaded #{schemas.length} schemas from #{filename}"
+  end
+end
+----
+
+==== Integration with CLI commands
+
+Schema manifests are supported by several CLI commands:
+
+===== Benchmarking with manifests
+
+[source,sh]
+----
+# Benchmark all schemas in a manifest
+expressir benchmark schemas.yml --verbose
+
+# Benchmark with caching
+expressir benchmark-cache schemas.yml --cache_path /tmp/cache.bin
+----
+
+===== Coverage analysis with manifests
+
+[source,sh]
+----
+# Analyze coverage for all schemas in manifest
+expressir coverage schemas.yml
+
+# With output format and exclusions
+expressir coverage schemas.yml --format json --exclude=TYPE:SELECT
+----
+
+
 
 == Contributing
 

data/bin/rspec

@@ -15,7 +15,8 @@ ENV["BUNDLE_GEMFILE"] ||= File.expand_path("../../Gemfile",
 bundle_binstub = File.expand_path("bundle", __dir__)
 
 if File.file?(bundle_binstub)
-  if File.read(bundle_binstub, 300).include?("This file was generated by Bundler")
+  if File.read(bundle_binstub,
+               300).include?("This file was generated by Bundler")
     load(bundle_binstub)
   else
     abort("Your `bin/bundle` was not generated by Bundler, so this binstub cannot run.

data/docs/liquid_drops.adoc

@@ -249,7 +249,7 @@ Attributes:
 `attributes`:: Array of AttributeDrop objects
 `unique_rules`:: Array of UniqueRuleDrop objects
 `where_rules`:: Array of WhereRuleDrop objects
-`informal_propositions`:: Array of RemarkItemDrop objects
+`informal_propositions`:: Array of InformalPropositionRule objects
 
 ==== FunctionDrop
 

data/expressir.gemspec

@@ -31,8 +31,6 @@ Gem::Specification.new do |spec|
     end
   end
 
-  spec.test_files = `git ls-files -- {spec}/*`.split("\n")
-
   spec.add_dependency "base64"
   spec.add_dependency "benchmark-ips"
   spec.add_dependency "csv"

data/lib/expressir/benchmark.rb

@@ -146,7 +146,8 @@ module Expressir
 
         # Measure cache reading time
         cache_read_time = ::Benchmark.measure do
-          results[:cached_repository] = Expressir::Express::Cache.from_file(cache_path)
+          results[:cached_repository] =
+            Expressir::Express::Cache.from_file(cache_path)
         end
         results[:cache_read_time] = cache_read_time.real
 
@@ -287,8 +288,10 @@ module Expressir
           }
           puts JSON.generate(result)
         when "csv"
-          headers = ["Files", "Schemas", "Objects", "Total Time (s)", "Avg Time (s)", "Objects/s"]
-          values = [count, schema_count, total_objects, total_time.round(4), avg_time.round(4), objects_per_second]
+          headers = ["Files", "Schemas", "Objects", "Total Time (s)",
+                     "Avg Time (s)", "Objects/s"]
+          values = [count, schema_count, total_objects, total_time.round(4),
+                    avg_time.round(4), objects_per_second]
 
           puts headers.join(",")
           puts values.join(",")