article_fixture_gen 0.1.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 10ed666ba0848073a4ecb39cf4fb96a9791e0c5f
+  data.tar.gz: babc44735968ddd244c7f638420aaa6f8529bf7d
+SHA512:
+  metadata.gz: b702163928ebce2462dc13c86896fe6ee3292e971dd5f80c018df61e2d9d9b381b43446c5d438623458791c50bc3b27c15d90cc29d8bbf383ccab7d0a9012995
+  data.tar.gz: 167d8cb59264aefe445bab24f39a64a66f0b1d63f6503d10e21901682c3261b7a4cf84637e9211036fda84c3efe76f470123c9690a357910042991126fd844db

data/.gitignore

@@ -0,0 +1,15 @@
+/.bundle/
+/.yardoc
+/Gemfile.lock
+/_yardoc/
+/coverage/
+/doc/
+/log/
+/o-rdoc/
+/pkg/
+/spec/reports/
+/tmp/
+/bin/
+!/bin/benchmarks
+!/bin/console
+!/bin/setup

data/.rubocop.yml

@@ -0,0 +1,6 @@
+
+AllCops:
+  TargetRubyVersion: 2.3
+
+Style/Alias:
+  Enabled: false

data/.travis.yml

@@ -0,0 +1,5 @@
+sudo: false
+language: ruby
+rvm:
+  - 2.3.1
+before_install: gem install bundler -v 1.12.5

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,49 @@
+# Contributor Code of Conduct
+
+As contributors and maintainers of this project, and in the interest of
+fostering an open and welcoming community, we pledge to respect all people who
+contribute through reporting issues, posting feature requests, updating
+documentation, submitting pull requests or patches, and other activities.
+
+We are committed to making participation in this project a harassment-free
+experience for everyone, regardless of level of experience, gender, gender
+identity and expression, sexual orientation, disability, personal appearance,
+body size, race, ethnicity, age, religion, or nationality.
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery
+* Personal attacks
+* Trolling or insulting/derogatory comments
+* Public or private harassment
+* Publishing other's private information, such as physical or electronic
+  addresses, without explicit permission
+* Other unethical or unprofessional conduct
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+By adopting this Code of Conduct, project maintainers commit themselves to
+fairly and consistently applying these principles to every aspect of managing
+this project. Project maintainers who do not follow or enforce the Code of
+Conduct may be permanently removed from the project team.
+
+This code of conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community.
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting a project maintainer at jdickey@seven-sigma.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. Maintainers are
+obligated to maintain confidentiality with regard to the reporter of an
+incident.
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 1.3.0, available at
+[http://contributor-covenant.org/version/1/3/0/][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/3/0/

data/Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in article_fixture_gen.gemspec
+gemspec

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2016 Jeff Dickey
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,220 @@
+# ArticleFixtureGen
+
+This Gem implements a utility, `article_fixture_gen`, which generates blog-style article/post [*fixture*](https://en.wikipedia.org/wiki/Test_fixture) data for use in development testing. Initially, the output is in [YAML](https://en.wikipedia.org/wiki/YAML) format.
+
+Why another article-data generator? This optionally generates "marker tag pairs" in the articles' body mark­up. These in turn are used to simulate user action affecting data; see below for a more complete descrip­tion. This feature was the original justification for developing the utility.
+
+----
+
+## Contents
+
+1. [Installation](#Installation)
+2. [Usage](#Usage)
+3. [Options](#Options)
+   1. [Command-Line Options](#command-line-options)
+   2. [Configuration-File Options](#configuration-file-options)
+4. [What Are Marker Tag Pairs?](#what-are-marker-tag-pairs-)
+   1. [Single-Marker Tag Pair](#single-marker-tag-pair)
+   2. [Paired-Marker Tag Pair](#paired-marker-tag-pair)
+5. [Article Fixture-Data Format](#article-fixture-data-format)
+6. [Development](#development)
+   1. [Running Tests](#running-tests)
+   2. [Feasible Future Features](#feasible-future-features)
+7. [Contributing](#contributing)
+   1. [Process](#process)
+   2. [Notes on Contributing](#notes-on-contributing)
+8. [License](#license)
+
+----
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'article_fixture_gen'
+```
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install article_fixture_gen
+
+## Usage
+
+From the command line, running
+
+```
+$ article_fixture_gen
+```
+
+with no existing configuration as described below, will produce YAML output, sent to standard output, for five *articles* that can then be loaded to create test-fixture entities in your application development.
+
+## Options
+
+Each of these options may be specified either from the command line or from a configuration file. Configuration specified on the command line overrides conflicting settings specified in a configuration file; in other words, the effective value of a particular option is determined based on
+
+1. the specified default value, which *may* be overridden by
+2. a value specified in a configuration file, which may be overridden by
+3. a value specified on the command line.
+
+Specifying an invalid value for any setting in a configuration file and/or on the command line will cause the invalid value to be ignored.
+
+For any option which is one of a pair of min/max options, such as `--para-count-min` and `--para-count-max`, if the effective value of the `*-min` setting is *greater than* the effective value of the`*-max` setting, then execution will be aborted with a suitable error message. Specifying the same effective value for both will, of course, function as a fixed value, eliminating randomised variation. When the `*-min` and `*-max` settings have different values, then the value used at any given time will be a random value between the minimum and maximum values, inclusive.
+
+### Command-Line Options
+
+#### `--article-count`
+
+Specifies the number of [article fixtures](#article-fixture-data-format) to generate. Valid values are positive integers; the default is 5 (equivalent to `--article-count 5`). Not specifying the option, or specifying an invalid value, will use the default.
+
+#### `—config`
+
+Specifies the filename of a [configuration file](#configuration-file-options) containing settings for this utility. If no configura­tion file is specified, and one exists in the `afg-config.yml` file in the current directory, it will be used.
+
+#### `—generate-config`
+
+Specifies the filename of a [configuration file](#configuration-file-options) to which all currently-effective option settings will be written. If the filename specified here is the same as that specified for the `—config` option above, then the file will be written to only after any existing settings are read. This allows the user to, for example, set the one or two options that she knows she cares about, generate a full configuration file with all settings, and experiment from there.
+
+#### `--para-count-max`
+
+Specifies the maximum number of (HTML) paragraphs in each generated fixture. This defaults to 10 (equivalent to `--para-count-max 10`) and, if specified, must be at least 1.
+
+#### `--para-count-min`
+
+Specifies the minimum number of (HTML) paragraphs in each generated fixture. This defaults to 2 (equivalent to `--para-count-min 2` and, if specified, must be at least 1.
+
+#### `--pmtp-count`
+
+Specifies the number of [paired-marker tag](#paired-marker-tag-pair) pairs to generate. This defaults to 2 (equivalent to `--pmtp-count 2`) and, if specified, may be any integer greater than or equal to 0. (Note that a combination of short content (paragraph/sentence count) with a high pMTP count is inadvisa­ble, as each pMTP **must** contain one or more words and each pMTP **must not** overlap another.)
+
+#### `--pmtp-text`
+
+Specifies the text portion of [paired-marker tag](#paired-marker-tag-pair) pairs' `id` attribute values. This defaults to `paired-mtp` (thus equivalent to specifying `--pmtp-text paired-mtp`) and, if specified, may be any non-empty contiguous text string made up of alphabetic characters optionally interspersed with hyphen (`-`) characters, so long as neither the first nor last characters are hyphens.
+
+#### `--sent-count-max`
+
+Specifies the maximum number of sentences in each paragraph within each generated fixture. This defaults to 8 (equivalent to `--sent-count-max 8`) and, if specified, must be at least 1.
+
+#### `--sent-count-min`
+
+Specifies the minimum number of sentences in each paragraph within each generated fixture. This defaults to 1 (equivalent to `--sent-count-min 1`), which is the minimum allowed value.
+
+#### `--smtp-count`
+
+Specifies the number of [single-marker tag](#single-marker-tag-pair) pairs to generate within the content. This defaults to 4 (equivalent to `--smtp-count 4`) and, if specified, may be any integer greater than or equal to 0. A relatively high sMTP/word count ratio doesn't have the same impact that it does for pMTPs, since it's permissible to have multiple immediately adjacent single-marker tag pairs.
+
+#### `--smtp-text`
+
+Specifies the text portion of [single-marker tag](#single-marker-tag-pair) pairs' `id` attribute values. This defaults to `single-mtp` (thus equivalent to specifying `--smtp-text single-mtp`) and, if specified, may be any non-empty contiguous text string made up of alphabetic characters optionally interspersed with hyphen (`-`) characters, so long as neither the first nor last characters are hyphens.
+
+### Configuration-File Options
+
+Option settings may be defined in a YAML-formatted configuration file and loaded into the utili­ty via the `—config` command-line option. An example configuration file which simply lists all de­fault settings is shown below:
+
+```yaml
+---
+:article_count: 5
+:para_count:
+  :max: 10
+  :min: 2
+:pmtp_count: 2
+:pmtp_text: paired-mtp
+:sent_count:
+  :max: 8
+  :min: 1
+:smtp_count: 4
+:smtp_text: single-mtp
+```
+
+## What Are Marker Tag Pairs?
+
+A *marker tag pair*, or *MTP,* is a specifically-formatted `<a></a>` tag pair, where
+
+1. no content separates the opening and closing tags;
+2. the opening tag has an `href` attribute whose value is the empty string; and
+3. the opening tag has an `id` attribute, whose value is formatted differently based on whether it is a single-marker or paired-marker tag pair, but in any case will start with a sequence of text characters (alphabetic or hyphens), followed by a
+
+### Single-Marker Tag Pair
+
+A single-marker tag pair (*sMTP*) is, logically enough, one `<a></a>` tag pair, where the `id` attri­bute of the opening tag follows the format `TEXT-uuid`, where `TEXT` can be any sequence of alphabetic characters, possibly intermixed with hyphen (`-`) characters. The `uuid` placeholder represents a [UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier).
+
+### Paired-Marker Tag Pair
+
+A paired-marker tag pair (*pMTP*) is a sequence of two `<a></a>` tag pairs, where the `id` attribute of each opening tag follows the format `TEXT-uuid-begin` for the first of the two tag pairs, and `TEXT-uuid-end` for the second. The `TEXT` and `uuid` placeholders follow the same conven­tions as for sMTPs, with the restriction that both tag pairs' `TEXT` and `uuid` placeholders **must** be identical, and the `-begin` MTP **must** occur before the `-end` MTP.
+
+## Article Fixture-Data Format
+
+Each conceptual Article has the following attributes, included in the YAML output:
+
+1. A `:title`, which is a simple text string of between three and ten (random) words;
+2. An `:author_name`, which is a text string, containing a randomly-generated given and "family" name fol­lowing simple Western convention;
+3. A `:body`, which is a string of (valid, well-formed) HTML (as XHTML/HTML5) content comprising one or more `<p></p>` tag pairs with random generated text inside the paragraphs. Optional settings may cause additional HTML to be inserted into the paragraphs' text; however, each is still guaranteed to be valid and well-formed. Note that multiple paragraphs *are not* enclosed within a containing `<div></div> or other tag pair; if the HTML tool you use (such as [Ox](https://github.com/ohler55/ox)) chokes on such multiple elements without a shared containing element, you'll need additional processing once the YAML has been parsed;
+4. An array of `:keywords`, which are zero to at most ten random short strings of one or more words each. There is no guarantee that any two generated Article entries will share any keywords, but no keywords will be repeated within any given Article;
+5. An `:image_url`, which is a string in the form `http://www.example.com/image_NUM.FMT`, where `NUM` is text for a one- to four-digit number (1 to 9999 inclusive) and `FMT` is either `png` or `jpg`. Both components are randomly selected each time;
+6. A `:created_at` timestamp, which is a YAML-formatted timestamp with sub-second (formatted as pico­second) resolution;
+
+Your Article may not need all of these fields; they were used for different applications within our organisa­tion. Future releases are expected to support filtering the then-supported attributes.
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies (which as of now must already be in­stalled on your local system). Then, run `bin/rake test` to run the tests, or `bin/rake` to run tests and, if tests are successful, further static-analysis tools ([RuboCop](https://github.com/bbatsov/rubocop), [Flay](https://github.com/seattlerb/flay), [Flog](https://github.com/seattlerb/flog), and [Reek](https://github.com/troessner/reek)).
+
+To install *your build* of this Gem onto your local machine, run `bin/rake install`. We recom­mend that you uninstall any previously-installed "official" Gem to increase your confi­dence that your tests are running against your build. You should then be able to run the `article_fixture_gen` command-line tool.
+
+### Running Tests
+
+Running tests *other than command-line tests* (within the `test/exe/article_fixture_gen/` directory) works just as you would expect for individual MiniTest::Spec test scripts; you can run a command line such as `ruby test/article_fixture_gen/data/article_test.rb` to run a single test-spec file. Also, running `rake` and `rake test` works just as you'd expect for running the complete set of tests.
+
+To run individual command-line tests, two changes are necessary:
+
+1. Install your current version of the Gem in your local Gem repo with the command line `rake install`;
+2. After successfully installing, run a single test prefixing the command line with `bundle exec`, as in `bundle exec ruby test/exe/article_fixture_gen/version_test.rb`.
+
+If anyone knows how to streamline this, to write the command-line tests so that they can be run from the command line without `bundle exec` as is done for all other tests, *please* submit a pull request!
+
+### Feasible Future Features
+
+#### Suppressing Field Output
+
+The attributes specified above may not be necessary in all uses of the utility. To suppress out­put of undesired fields, new options may be supported; for example, `--no-image-url` would sup­press the `:image_url` attribute.
+
+#### Other Ideas?
+
+Do you see something we missed that you'd find useful? Open an [issue and PR](#process) and let's have a chat about it!
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/jdickey/article_fixture_gen. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to ad­here to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
+
+### Process
+
+If you wish to submit a new feature to the Gem, please [open an issue](https://github.com/jdickey/article_fixture_gen/issues/new) to discuss your idea with the main­tainer and other interested community members. Issue threads are a great place to thrash out the details of what you're trying to accomplish and how your work would affect other code and/or community mem­bers. If you need help with something, or aren't sure how to choose between different ideas to accomplish some detail of what you're setting out to do, this is the place to discuss that. There is *no such thing as a stu­pid question that you don't know the answer to* (once you've researched in your search engine of choice, of course; please do respect people's time and attention).
+
+The processes for proposing a new feature or a fix to an open bug-report issue are very similar:
+
+1. Make sure that you have forked this Gem's [repository on GitHub](https://github.com/jdickey/article_fixture_gen) to your own GitHub account. (If you don't yet have a GitHub account, [join](https://github.com/join?source=header-home); it's free.)
+2. If you're proposing a new feature, [open an issue](https://github.com/jdickey/article_fixture_gen) as suggested above. If you're addressing an existing issue, *thanks;* you don't need to open a new one.
+3. Clone *your* copy of the repo to your local development system.
+4. Create a new Git branch for your work. It's best to give it a reasonably short name that's suggestive of what you're specifically trying to accomplish.
+   1. If you're adding a new feature, please use a descriptive name for your feature branch. `output-as-fooml` is a much more descriptive name than `my-branch` when you're working on adding the ability to output FooML instead of YAML, for example.
+   2. If you're adding a fix for an existing issue *other than* a new feature which you've opened to propose a new feature, then use the branch name `issue-nnnn`, where `nnnn` is the issue number in Github. For example, if you're working on Issue #4972, then you'd ordinarily name your branch `issue-4172`.
+   3. **Do not** work on your copy of the `master` branch! Any pull request (see below) that you later submit for changes you've made on `master` will be rejected, and you will be asked to submit your pro­posed changes on a branch that branches from a commit on the upstream `master` branch.
+5. Now write great (tests and) code!
+6. As soon as you have something to show, *even if it's not complete yet* (but it passes what tests you have), [push your branch](https://help.github.com/articles/pushing-to-a-remote/) to *your forked repo* on GitHub and open a [new pull request](https://github.com/jdickey/article_fixture_gen/compare) ("PR") for *your branch* com­pared to `master` on the [upstream](https://github.com/jdickey/article_fixture_gen) repository. That lets the maintainer and other community mem­bers review your code and tests, comment, help out, and so on.
+7. Continuing with your pull request, it's usually better if you make small, incremental changes in each commit in a sequence. We (endeavour to) practice [behaviour-driven development](https://en.wikipedia.org/wiki/Behavior-driven_development): write tests for the simplest thing that could possibly work; see the tests fail; then make them pass, commit, and go on to the next simplest thing. Don't get hung up on lots of refac­toring until you have code that does everything you want it to do; once you have a legiti­mately complete green bar, *that's* the time to apply SOLID principles and patterns to DRY things up. Better to have (temporary) duplication than choose the wrong abstraction.
+
+### Notes on Contributing
+
+Don't be discouraged if it takes several commits to complete your work and then several more to get everybody agreeing that it's complete and well done. ("Useful" and "worth adding" should have been settled at the issue stage, before you started working on your PR.) That's because…
+
+When pull requests are *merged* into the `master` branch, they are [*squashed*](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History#Squashing-Commits) so that all changes are applied to `master` in a single commit. This means that, even if you have a dozen or more commits in your PR where you've been *very* incremental, and even changed direction once or twice, what matters is the final result; not what it took to get there.
+
+Once your PR has been merged, it's a good idea to pull the upstream `master` branch to your development system (`git pull upstream master`) and then push it to your fork (`git push origin master`). (What? You don't *have* an `upstream` remote as shown by `git remote -v`? Run the command `git remote add upstream https://github.com/TheProlog/prolog_minitest_matchers.git` from your local development directory, and now you do.)
+
+## License
+
+The Gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).

data/Rakefile

@@ -0,0 +1,48 @@
+
+require "bundler/gem_tasks"
+require "rake/testtask"
+
+require 'rake/tasklib'
+require 'flay'
+require 'flay_task'
+require 'tasks/prolog_flog_task'
+require 'reek/rake/task'
+require 'rubocop/rake_task'
+
+Rake::TestTask.new(:test) do |t|
+  t.libs << "test"
+  t.libs << "lib"
+  t.test_files = FileList['test/**/*_test.rb']
+end
+
+RuboCop::RakeTask.new(:rubocop) do |task|
+  task.patterns = [
+    'lib/**/*.rb',
+    'test/**/*.rb'
+  ]
+  task.formatters = ['simple', 'd']
+  task.fail_on_error = true
+  # task.options << '--rails'
+  task.options << '--display-cop-names'
+  end
+
+  Reek::Rake::Task.new do |t|
+  t.config_file = 'config.reek'
+  t.source_files = 'lib/**/*.rb'
+  t.reek_opts = '--sort-by smelliness -s'
+end
+
+FlayTask.new do |t|
+  t.verbose = true
+  t.dirs = %w(app lib)
+end
+
+FlogTask.new do |t|
+  t.verbose = true
+  t.threshold = 600 # default is 200
+  t.methods_only = true
+  t.dirs = %w(lib)
+end
+
+task(:default).clear
+task default: [:test, :rubocop, :flay, :flog, :reek]

data/article_fixture_gen.gemspec

@@ -0,0 +1,55 @@
+# coding: utf-8
+lib = File.expand_path('../lib', __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require 'article_fixture_gen/version'
+
+Gem::Specification.new do |spec|
+  spec.name          = "article_fixture_gen"
+  spec.version       = ArticleFixtureGen::VERSION
+  spec.authors       = ["Jeff Dickey"]
+  spec.email         = ["jdickey@seven-sigma.com"]
+  spec.required_ruby_version = ">= 2.3.0"
+
+  spec.summary       = %q{Generate blog post/article fixture data, with embedded marker tag pairs.}
+  # spec.description   = %q{TODO: Write a longer description or delete this line.}
+  spec.homepage      = "https://github.com/jdickey/article_fixture_gen"
+  spec.license       = "MIT"
+
+  # Prevent pushing this gem to RubyGems.org. To allow pushes either set the 'allowed_push_host'
+  # to allow pushing to a single host or delete this section to allow pushing to any host.
+  # if spec.respond_to?(:metadata)
+  #   spec.metadata['allowed_push_host'] = "TODO: Set to 'http://mygemserver.com'"
+  # else
+  #   raise "RubyGems 2.0 or newer is required to protect against public gem pushes."
+  # end
+
+  spec.files         = `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
+  spec.bindir        = "exe"
+  spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
+  spec.require_paths = ["lib"]
+
+  spec.add_dependency "awesome_print", "~> 1.7", ">= 1.7.0"
+  spec.add_dependency "ffaker", "~> 2.2", ">= 2.2.0"
+  spec.add_dependency "ox", "~> 2.4", ">= 2.4.4"
+  spec.add_dependency "prolog-dry_types", "~> 0.3", ">= 0.3.0"
+  spec.add_dependency "semantic_logger", "~> 3.3", ">= 3.3.0"
+  spec.add_dependency "trollop", "~> 2.1", ">= 2.1.2"
+
+  spec.add_development_dependency "bundler", "~> 1.12", ">= 1.12.5"
+  spec.add_development_dependency "rake", "~> 11.2", ">= 11.2.2"
+  spec.add_development_dependency "minitest", "~> 5.9", ">= 5.9.0"
+
+  spec.add_development_dependency "minitest-matchers", "~> 1.4", ">= 1.4.1"
+  spec.add_development_dependency "minitest-profile" # , "~> 1.4", ">= 1.4.1"
+  spec.add_development_dependency "minitest-reporters", "~> 1.1", ">= 1.1.11"
+  spec.add_development_dependency "minitest-tagz", "~> 1.5", ">= 1.5.1"
+  spec.add_development_dependency "prolog_minitest_matchers", "~> 0.3", ">= 0.3.1"
+
+  spec.add_development_dependency "flay", "~> 2.8", ">= 2.8.0"
+  spec.add_development_dependency "flog", "~> 4.4", ">= 4.4.0"
+  spec.add_development_dependency "reek", "~> 4", ">= 4.2.4"
+  spec.add_development_dependency "rubocop", "~> 0.42", ">= 0.42.0"
+  spec.add_development_dependency "simplecov", "~> 0.12", ">= 0.12.0"
+  spec.add_development_dependency "pry-byebug", "~> 3.4", ">= 3.4.0"
+  spec.add_development_dependency "pry-doc", "~> 0.9", ">= 0.9.0"
+end

data/bin/console

@@ -0,0 +1,14 @@
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "article_fixture_gen"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require "irb"
+IRB.start

data/bin/setup

@@ -0,0 +1,16 @@
+#!/usr/bin/env bash
+# set -euo pipefail
+# IFS=$'\n\t'
+# set -vx
+
+rm -rf .bundle Gemfile.lock
+
+bundle install --local
+
+if [[ -d $RBENV_ROOT ]]
+then
+  rbenv rehash
+fi
+
+mkdir -p log
+bundle binstub --force flay flog pry rake reek rubocop

data/config.reek

@@ -0,0 +1,8 @@
+
+LongParameterList:
+  max_params: 4  # If it's good enough for Sandi, it's good enough for us.
+
+# NestedIterators:
+#   max_allowed_nesting: 2
+#   ignore_iterators:
+#     - lambda

data/data/all_specs.yml

@@ -0,0 +1,127 @@
+---
+- !ruby/object:ArticleFixtureGen::Exe::Trollop::OptionSpec
+  item: !ruby/object:ArticleFixtureGen::Exe::Trollop::OptionSpecItem
+    key: :article_count
+    desc: Number of article fixtures to generate
+    options:
+      :default: 5
+      :short: :none
+      :type: :int
+      :long: article-count
+      :multi: false
+      :desc: Number of article fixtures to generate
+- !ruby/object:ArticleFixtureGen::Exe::Trollop::OptionSpec
+  item: !ruby/object:ArticleFixtureGen::Exe::Trollop::OptionSpecItem
+    key: :config
+    desc: Modify default configuration by applying contents of a YAML file
+    options:
+      :type: :string
+      :short: :none
+      :long: config
+      :multi: false
+      :desc: Modify default configuration by applying contents of a YAML file
+- !ruby/object:ArticleFixtureGen::Exe::Trollop::OptionSpec
+  item: !ruby/object:ArticleFixtureGen::Exe::Trollop::OptionSpecItem
+    key: :generate_config
+    desc: Export configuration to a YAML file after initialisation is complete.
+    options:
+      :type: :string
+      :short: :none
+      :long: generate-config
+      :multi: false
+      :desc: Export configuration to a YAML file after initialisation is complete.
+- !ruby/object:ArticleFixtureGen::Exe::Trollop::OptionSpec
+  item: !ruby/object:ArticleFixtureGen::Exe::Trollop::OptionSpecItem
+    key: :para_count_max
+    desc: Maximum number of (HTML) paragraphs in each generated fixture.
+    options:
+      :default: 10
+      :short: :none
+      :type: :int
+      :long: para-count-max
+      :multi: false
+      :desc: Maximum number of (HTML) paragraphs in each generated fixture.
+- !ruby/object:ArticleFixtureGen::Exe::Trollop::OptionSpec
+  item: !ruby/object:ArticleFixtureGen::Exe::Trollop::OptionSpecItem
+    key: :para_count_min
+    desc: Minimum number of (HTML) paragraphs in each generated fixture.
+    options:
+      :default: 2
+      :short: :none
+      :type: :int
+      :long: para-count-min
+      :multi: false
+      :desc: Minimum number of (HTML) paragraphs in each generated fixture.
+- !ruby/object:ArticleFixtureGen::Exe::Trollop::OptionSpec
+  item: !ruby/object:ArticleFixtureGen::Exe::Trollop::OptionSpecItem
+    key: :pmtp_count
+    desc: Specifies the number of paired-marker tag pairs to generate.
+    options:
+      :default: 2
+      :short: :none
+      :type: :int
+      :long: pmtp-count
+      :multi: false
+      :desc: Specifies the number of paired-marker tag pairs to generate.
+- !ruby/object:ArticleFixtureGen::Exe::Trollop::OptionSpec
+  item: !ruby/object:ArticleFixtureGen::Exe::Trollop::OptionSpecItem
+    key: :pmtp_text
+    desc: Specifies the text portion of paired-marker tag pairs' :id attribute values.
+    options:
+      :default: paired-mtp
+      :short: :none
+      :type: :string
+      :long: pmtp-text
+      :multi: false
+      :desc: Specifies the text portion of paired-marker tag pairs' :id attribute
+        values.
+- !ruby/object:ArticleFixtureGen::Exe::Trollop::OptionSpec
+  item: !ruby/object:ArticleFixtureGen::Exe::Trollop::OptionSpecItem
+    key: :sent_count_max
+    desc: Specifies the maximum number of sentences in each paragraph within each
+      generated fixture.
+    options:
+      :default: 8
+      :short: :none
+      :type: :int
+      :long: sent-count-max
+      :multi: false
+      :desc: Specifies the maximum number of sentences in each paragraph within each
+        generated fixture.
+- !ruby/object:ArticleFixtureGen::Exe::Trollop::OptionSpec
+  item: !ruby/object:ArticleFixtureGen::Exe::Trollop::OptionSpecItem
+    key: :sent_count_min
+    desc: Specifies the minimum number of sentences in each paragraph within each
+      generated fixture.
+    options:
+      :default: 1
+      :short: :none
+      :type: :int
+      :long: sent-count-min
+      :multi: false
+      :desc: Specifies the minimum number of sentences in each paragraph within each
+        generated fixture.
+- !ruby/object:ArticleFixtureGen::Exe::Trollop::OptionSpec
+  item: !ruby/object:ArticleFixtureGen::Exe::Trollop::OptionSpecItem
+    key: :smtp_count
+    desc: Specifies the number of single-marker tag pairs to generate within the content.
+    options:
+      :default: 4
+      :short: :none
+      :type: :int
+      :long: smtp-count
+      :multi: false
+      :desc: Specifies the number of single-marker tag pairs to generate within the
+        content.
+- !ruby/object:ArticleFixtureGen::Exe::Trollop::OptionSpec
+  item: !ruby/object:ArticleFixtureGen::Exe::Trollop::OptionSpecItem
+    key: :smtp_text
+    desc: Specifies the text portion of single-marker tag pairs' :id attribute values.
+    options:
+      :default: single-mtp
+      :short: :none
+      :type: :string
+      :long: smtp-text
+      :multi: false
+      :desc: Specifies the text portion of single-marker tag pairs' :id attribute
+        values.

data/data/validations.yml

@@ -0,0 +1,35 @@
+---
+- :key: :para_count_max
+  :str: must be at least 1
+  :fails_with: "-> (options) { options[:para_count_max] < 1 }"
+- :key: :para_count_max
+  :str: must be >= the value for --para-count-min
+  :fails_with: "-> (options) { options[:para_count_max] < options[:para_count_min]
+    }"
+- :key: :para_count_min
+  :str: must be at least 1
+  :fails_with: "-> (options) { options[:para_count_min] < 1 }"
+- :key: :para_count_min
+  :str: must be <= the value for --para-count-max
+  :fails_with: "-> (options) { options[:para_count_max] < options[:para_count_min]
+    }"
+- :key: :pmtp_text
+  :str: may not be empty
+  :fails_with: "-> (options) { options[:pmtp_text].to_s.strip.empty? }"
+- :key: :sent_count_max
+  :str: must be at least 1
+  :fails_with: "-> (options) { options[:sent_count_max] < 1 }"
+- :key: :sent_count_max
+  :str: must be >= the value for --sent-count-min
+  :fails_with: "-> (options) { options[:sent_count_max] < options[:sent_count_min]
+    }"
+- :key: :sent_count_min
+  :str: must be at least 1
+  :fails_with: "-> (options) { options[:sent_count_min] < 1 }"
+- :key: :sent_count_min
+  :str: must be <= the value for --sent-count-max
+  :fails_with: "-> (options) { options[:sent_count_max] < options[:sent_count_min]
+    }"
+- :key: :smtp_text
+  :str: may not be empty
+  :fails_with: "-> (options) { options[:smtp_text].to_s.strip.empty? }"