cybertron 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 8be6125a4e7ec2acaad74513dcb0153a12fd21e34626610bf6f4eb48b2d571cd
+  data.tar.gz: 6944169b656572e7168ecc650d81ccdd656e1758e8b1869124a107ec46afe46d
+SHA512:
+  metadata.gz: f8bd247f9e822b7b8e315b05416e5882a3804a4b16c138329da47d09c94309760b1c1c8cd803e22ff6ac1a62a86dd5425c5df8534d56e4af7e94c8bd50cce792
+  data.tar.gz: 74478904943b9f53c3ea712a75de39859976a16709f8d34d1726e64ad7b3dcd86651705b1cd1bc596d01cd362591d87b9148638bef57adc876d99896df954250

data/.gitignore

@@ -0,0 +1,11 @@
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+
+# rspec failure tracking
+.rspec_status

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.travis.yml

@@ -0,0 +1,7 @@
+---
+sudo: false
+language: ruby
+cache: bundler
+rvm:
+  - 2.5.5
+before_install: gem install bundler -v 2.0.2

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+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.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at rajasegarc@freshdesk.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile

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

data/Gemfile.lock

@@ -0,0 +1,37 @@
+PATH
+  remote: .
+  specs:
+    cybertron (0.1.0)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    diff-lcs (1.3)
+    rake (10.5.0)
+    rspec (3.8.0)
+      rspec-core (~> 3.8.0)
+      rspec-expectations (~> 3.8.0)
+      rspec-mocks (~> 3.8.0)
+    rspec-core (3.8.2)
+      rspec-support (~> 3.8.0)
+    rspec-expectations (3.8.4)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.8.0)
+    rspec-mocks (3.8.1)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.8.0)
+    rspec-support (3.8.2)
+    thor (0.20.3)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  bundler (~> 2.0)
+  cybertron!
+  rake (~> 10.0)
+  rspec (~> 3.0)
+  thor
+
+BUNDLED WITH
+   2.0.2

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2019 Rajasegar
+
+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,43 @@
+# Cybertron
+
+Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file `lib/cybertron`. To experiment with that code, run `bin/console` for an interactive prompt.
+
+TODO: Delete this and the text above, and describe your gem
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'cybertron'
+```
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install cybertron
+
+## Usage
+
+TODO: Write usage instructions here
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/cybertron. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+
+## Code of Conduct
+
+Everyone interacting in the Cybertron project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/cybertron/blob/master/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -0,0 +1,6 @@
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+task :default => :spec

data/bin/console

@@ -0,0 +1,14 @@
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "cybertron"
+
+# 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(__FILE__)

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/cybertron.gemspec

@@ -0,0 +1,33 @@
+lib = File.expand_path("lib", __dir__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require "cybertron/version"
+
+Gem::Specification.new do |spec|
+  spec.name          = "cybertron"
+  spec.version       = Cybertron::VERSION
+  spec.authors       = ["Rajasegar"]
+  spec.email         = ["rajasegar.c@gmail.com"]
+
+  spec.summary       = "Create Ruby Transformers from Cybertron"
+  spec.description   = "Cybertron is a Ruby CLI to create codemods"
+  spec.homepage      = "https://github.com/rajasegar/cybertron"
+  spec.license       = "MIT"
+
+  spec.metadata["homepage_uri"] = spec.homepage
+  spec.metadata["source_code_uri"] = "https://github.com/rajasegar/cybertron"
+
+  # Specify which files should be added to the gem when it is released.
+  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
+  spec.files         = Dir.chdir(File.expand_path('..', __FILE__)) do
+    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
+  end
+  spec.bindir        = "exe"
+  spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
+  spec.require_paths = ["lib"]
+
+  spec.add_development_dependency "thor"
+
+  spec.add_development_dependency "bundler", "~> 2.0"
+  spec.add_development_dependency "rake", "~> 10.0"
+  spec.add_development_dependency "rspec", "~> 3.0"
+end

data/exe/cybertron

@@ -0,0 +1,7 @@
+#!/usr/bin/env ruby
+
+$LOAD_PATH.unshift(File.expand_path('../../lib', __FILE__))
+require 'cybertron/cli'
+
+result = Cybertron::CLI.start(ARGV)
+exit(result ? 0 : 1)

data/lib/cybertron.rb

@@ -0,0 +1,6 @@
+require "cybertron/version"
+
+module Cybertron
+  class Error < StandardError; end
+  # Your code goes here...
+end

data/lib/cybertron/cli.rb

@@ -0,0 +1,42 @@
+# frozen_string_literal: true
+
+require 'optparse'
+require 'cybertron/options'
+require 'cybertron/version'
+require 'thor'
+require 'fileutils'
+
+module Cybertron
+  # CLI class
+  class CLI < Thor
+    include Thor::Actions
+
+    def self.source_root
+      File.expand_path('../templates', __dir__)
+    end
+
+    desc ' new <project-name>', 'Create a new Codemod project'
+    def new(name)
+      puts "Creating new project: #{name}"
+      FileUtils.mkdir_p "#{name}/transforms"
+      FileUtils.mkdir_p "#{name}/spec"
+      template 'rspec.tt', "#{name}/.rspec"
+      template 'spec_helper.tt', "#{name}/spec/spec_helper.rb"
+      template 'Rakefile.tt', "#{name}/Rakefile"
+      template 'readme.tt', "#{name}/README.md"
+    end
+
+    desc ' generate <name-of-transform>', 'Generate a new transform'
+    def generate(name)
+      @name = name
+      puts "Creating new transform: #{name}"
+      FileUtils.mkdir_p "transforms/#{name}"
+      FileUtils.mkdir_p "transforms/#{name}/fixtures"
+      template 'transform.tt', "transforms/#{name}/transform.rb"
+      template 'transform_spec.tt', "spec/#{name}_spec.rb"
+      template 'fixture_input.tt', "transforms/#{name}/fixtures/basic_input.rb"
+      template 'fixture_output.tt', "transforms/#{name}/fixtures/basic_output.rb"
+      template 'readme_transform.tt', "transforms/#{name}/README.md"
+    end
+  end
+end

data/lib/cybertron/options.rb

@@ -0,0 +1,9 @@
+# frozen_string_literal: true
+
+module Cybertron
+  class Options
+
+    def initialize
+    end
+  end
+end

data/lib/cybertron/version.rb

@@ -0,0 +1,3 @@
+module Cybertron
+  VERSION = "0.1.0"
+end

data/lib/templates/Rakefile.tt

@@ -0,0 +1,6 @@
+require 'rake'
+require 'rspec/core/rake_task'
+
+RSpec::Core::RakeTask.new(:spec) 
+
+task :default  => :spec

data/lib/templates/fixture_input.tt

@@ -0,0 +1,9 @@
+tips = [
+  "Click on any AST node with a '+' to expand it",
+
+  "Hovering over a node highlights the \
+corresponding part in the source code",
+]
+def print_tips
+  tips.each { |key, value| print "Tip #{key}: #{value}" }
+end

data/lib/templates/fixture_output.tt

@@ -0,0 +1,9 @@
+spit = [
+  "Click on any AST node with a '+' to expand it",
+
+  "Hovering over a node highlights the \
+corresponding part in the source code",
+]
+def spit_tnirp
+  tips.each { |key, value| print "Tip #{key}: #{value}" }
+end

data/lib/templates/readme.tt

@@ -0,0 +1,14 @@
+# <%= @name %>
+
+
+## Usage
+
+```rb
+codeshift -t <%= @name %>/<transform-name>/transform.rb <path>
+```
+
+## Run tests
+
+```rb
+rake
+```

data/lib/templates/readme_transform.tt

@@ -0,0 +1,19 @@
+# <%= @name %>
+
+
+## Usage
+
+```rb
+codeshift -t <%= @name %>/transform.rb <path>
+```
+
+## Input / Output
+
+<!--FIXTURES_TOC_START-->
+* [basic-imports](#basic-imports)
+* [existing-import](#existing-import)
+* [integration-helpers](#integration-helpers)
+<!--FIXTURES_TOC_END-->
+
+<!--FIXTURES_CONTENT_START-->
+<!--FIXTURES_CONTENT_END-->

data/lib/templates/rspec.tt

@@ -0,0 +1 @@
+--require spec_helper

data/lib/templates/spec_helper.tt

@@ -0,0 +1,98 @@
+# This file was generated by the `rspec --init` command. Conventionally, all
+# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.
+# The generated `.rspec` file contains `--require spec_helper` which will cause
+# this file to always be loaded, without a need to explicitly require it in any
+# files.
+#
+# Given that it is always loaded, you are encouraged to keep this file as
+# light-weight as possible. Requiring heavyweight dependencies from this file
+# will add to the boot time of your test suite on EVERY test run, even for an
+# individual file that may not need all of that loaded. Instead, consider making
+# a separate helper file that requires the additional dependencies and performs
+# the additional setup, and require it from the spec files that actually need
+# it.
+#
+# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
+RSpec.configure do |config|
+  # rspec-expectations config goes here. You can use an alternate
+  # assertion/expectation library such as wrong or the stdlib/minitest
+  # assertions if you prefer.
+  config.expect_with :rspec do |expectations|
+    # This option will default to `true` in RSpec 4. It makes the `description`
+    # and `failure_message` of custom matchers include text for helper methods
+    # defined using `chain`, e.g.:
+    #     be_bigger_than(2).and_smaller_than(4).description
+    #     # => "be bigger than 2 and smaller than 4"
+    # ...rather than:
+    #     # => "be bigger than 2"
+    expectations.include_chain_clauses_in_custom_matcher_descriptions = true
+  end
+
+  # rspec-mocks config goes here. You can use an alternate test double
+  # library (such as bogus or mocha) by changing the `mock_with` option here.
+  config.mock_with :rspec do |mocks|
+    # Prevents you from mocking or stubbing a method that does not exist on
+    # a real object. This is generally recommended, and will default to
+    # `true` in RSpec 4.
+    mocks.verify_partial_doubles = true
+  end
+
+  # This option will default to `:apply_to_host_groups` in RSpec 4 (and will
+  # have no way to turn it off -- the option exists only for backwards
+  # compatibility in RSpec 3). It causes shared context metadata to be
+  # inherited by the metadata hash of host groups and examples, rather than
+  # triggering implicit auto-inclusion in groups with matching metadata.
+  config.shared_context_metadata_behavior = :apply_to_host_groups
+
+  # The settings below are suggested to provide a good initial experience
+  # with RSpec, but feel free to customize to your heart's content.
+  # This allows you to limit a spec run to individual examples or groups
+  # you care about by tagging them with `:focus` metadata. When nothing
+  # is tagged with `:focus`, all examples get run. RSpec also provides
+  # aliases for `it`, `describe`, and `context` that include `:focus`
+  # metadata: `fit`, `fdescribe` and `fcontext`, respectively.
+  config.filter_run_when_matching :focus
+
+  # Allows RSpec to persist some state between runs in order to support
+  # the `--only-failures` and `--next-failure` CLI options. We recommend
+  # you configure your source control system to ignore this file.
+  #config.example_status_persistence_file_path = "spec/examples.txt"
+
+  # Limits the available syntax to the non-monkey patched syntax that is
+  # recommended. For more details, see:
+  #   - http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/
+  #   - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
+  #   - http://rspec.info/blog/2014/05/notable-changes-in-rspec-3/#zero-monkey-patching-mode
+  config.disable_monkey_patching!
+
+  # This setting enables warnings. It's recommended, but in some cases may
+  # be too noisy due to issues in dependencies.
+  config.warnings = true
+
+  # Many RSpec users commonly either run the entire suite or an individual
+  # file, and it's useful to allow more verbose output when running an
+  # individual spec file.
+  if config.files_to_run.one?
+    # Use the documentation formatter for detailed output,
+    # unless a formatter has already been configured
+    # (e.g. via a command-line flag).
+    config.default_formatter = "doc"
+  end
+
+  # Print the 10 slowest examples and example groups at the
+  # end of the spec run, to help surface which specs are running
+  # particularly slow.
+  config.profile_examples = 10
+
+  # Run specs in random order to surface order dependencies. If you find an
+  # order dependency and want to debug it, you can fix the order by providing
+  # the seed, which is printed after each run.
+  #     --seed 1234
+  config.order = :random
+
+  # Seed global randomization in this process using the `--seed` CLI option.
+  # Setting this allows you to use `--seed` to deterministically reproduce
+  # test failures related to randomization by passing the same `--seed` value
+  # as the one that triggered the failure.
+  Kernel.srand config.seed
+end

data/lib/templates/transform.tt

@@ -0,0 +1,16 @@
+# frozen_string_literal: true
+
+require 'parser/current'
+
+# Your Transform Class should always extend from
+# Parser:: TreeRewriter
+class <%= @name.capitalize %>Transform < Parser::TreeRewriter
+  def on_lvasgn(node)
+    # Reverse the variable names
+    replace(node.loc.name, node.children[0].to_s.reverse)
+  end
+
+  def on_def(node)
+    replace(node.loc.name, node.children[0].to_s.reverse)
+  end
+end

data/lib/templates/transform_spec.tt

@@ -0,0 +1,25 @@
+# frozen_string_literal: true
+
+require './transforms/<%= @name %>/transform.rb'
+RSpec.describe <%= @name.capitalize %>Transform do
+  describe '<%= @name.capitalize %> transform' do
+    Dir.glob('transforms/<%= @name %>/fixtures/*_input.rb').each do |input|
+      p input
+      it "transforms #{input}" do
+        source = File.read(input)
+
+        temp = Parser::CurrentRuby.parse(source)
+        rewriter = ConditionsTransform.new
+
+        buffer        = Parser::Source::Buffer.new('(example)')
+        buffer.source = source
+        # Rewrite the AST, returns a String with the new form.
+        transform = rewriter.rewrite(buffer, temp)
+
+        output_fixture = input.gsub('_input.rb', '_output.rb')
+        output = File.read(output_fixture)
+        expect(transform).to eq(output)
+      end
+    end
+  end
+end

metadata

@@ -0,0 +1,129 @@
+--- !ruby/object:Gem::Specification
+name: cybertron
+version: !ruby/object:Gem::Version
+  version: 0.1.0
+platform: ruby
+authors:
+- Rajasegar
+autorequire: 
+bindir: exe
+cert_chain: []
+date: 2019-09-19 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: thor
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: bundler
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '2.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '2.0'
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '10.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '10.0'
+- !ruby/object:Gem::Dependency
+  name: rspec
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.0'
+description: Cybertron is a Ruby CLI to create codemods
+email:
+- rajasegar.c@gmail.com
+executables:
+- cybertron
+extensions: []
+extra_rdoc_files: []
+files:
+- ".gitignore"
+- ".rspec"
+- ".travis.yml"
+- CODE_OF_CONDUCT.md
+- Gemfile
+- Gemfile.lock
+- LICENSE.txt
+- README.md
+- Rakefile
+- bin/console
+- bin/setup
+- cybertron.gemspec
+- exe/cybertron
+- lib/cybertron.rb
+- lib/cybertron/cli.rb
+- lib/cybertron/options.rb
+- lib/cybertron/version.rb
+- lib/templates/Rakefile.tt
+- lib/templates/fixture_input.tt
+- lib/templates/fixture_output.tt
+- lib/templates/readme.tt
+- lib/templates/readme_transform.tt
+- lib/templates/rspec.tt
+- lib/templates/spec_helper.tt
+- lib/templates/transform.tt
+- lib/templates/transform_spec.tt
+homepage: https://github.com/rajasegar/cybertron
+licenses:
+- MIT
+metadata:
+  homepage_uri: https://github.com/rajasegar/cybertron
+  source_code_uri: https://github.com/rajasegar/cybertron
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubyforge_project: 
+rubygems_version: 2.7.6.2
+signing_key: 
+specification_version: 4
+summary: Create Ruby Transformers from Cybertron
+test_files: []