rails_namespace_engine 0.1.0 → 0.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: ea1ba95da16e9ea926b0a3599bb628a77dc859a5
-  data.tar.gz: ea97a8ca3aab52fc3bb1c577c4c9cb466f75ba08
+  metadata.gz: 1df2cf5183bbe1f85e2d73816b832d9e518846df
+  data.tar.gz: c6e4b746d4c8968e49a41878e89660efd88a9c92
 SHA512:
-  metadata.gz: 48e0ed14d1f04ad03fb38476ebacc7351cf50dc5909364e608dd4e73dccabb05f1732cb7bf0f9c1f12569a23efd0f500df7b5c07b8ee41e5389de0a3d115141d
-  data.tar.gz: b3ff6171153b3c4ff4024e217a74709831f5e35d133d06a0f5e12082b0ad398c512a386ddd69c3264a56af80527840e16a5b8c1a75a3aaa78bf6a8aca17c683d
+  metadata.gz: 5bcaad91cce64e5e0e5a590f73947d11bf8b5d798509d8e199a0944d524b347a3f4e34fa3d00271a56c3908135ceb38dd048c25d63b849cc53a05621f85e7b92
+  data.tar.gz: 37a5124d67099ce9fd5d0505beed80df8b8f32654e2ca035d7c491cefcd59c6e45693ebc4e422e6efd41e137671d82bc254c985879d5f666083565e751fce822

data/lib/rails_namespace_engine.rb

@@ -35,7 +35,7 @@ class NamespaceEngine
       The first is the name of the namespace you wish to use.
       The second is the name used for the generated engine.
 
-      Ex. rne my_namespace my_engine.
+      Ex. namespace_engine my_namespace my_engine
 
       This script will run 'rails plugin new engine_name --mountable'.
       It then uses the provided namespace argument to restructure the file

data/lib/rails_namespace_engine/version.rb

@@ -1,3 +1,3 @@
 module RailsNamespaceEngine
-  VERSION = "0.1.0"
+  VERSION = "0.2.0"
 end

data/rails_namespace_engine.gemspec

@@ -10,8 +10,8 @@ Gem::Specification.new do |spec|
   spec.email         = ["nathaniel@m.ller.io"]
 
   spec.summary       = %q{Generate a rails engine with an extra layer of namespacing.}
-  spec.description   = %q{This script runs the rails plugin generator and then changes directory structure and file contents to prevent potential collisions with other engines.}
-  spec.homepage      = "http://m.ller.io"
+  spec.description   = %q{This script runs the rails plugin generator. It then changes the directory structure and file contents (based on provided namespacing and engine name) to prevent potential collisions with other engines.}
+  spec.homepage      = "https://github.com/nathaniel-miller/namespace_engine/"
   spec.license       = "MIT"
 
   # Prevent pushing this gem to RubyGems.org. To allow pushes either set the 'allowed_push_host'

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: rails_namespace_engine
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.2.0
 platform: ruby
 authors:
 - Nathaniel Miller
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-04-10 00:00:00.000000000 Z
+date: 2017-04-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -52,8 +52,9 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '3.0'
-description: This script runs the rails plugin generator and then changes directory
-  structure and file contents to prevent potential collisions with other engines.
+description: This script runs the rails plugin generator. It then changes the directory
+  structure and file contents (based on provided namespacing and engine name) to prevent
+  potential collisions with other engines.
 email:
 - nathaniel@m.ller.io
 executables:
@@ -61,18 +62,16 @@ executables:
 extensions: []
 extra_rdoc_files: []
 files:
-- CODE_OF_CONDUCT.md
 - Gemfile
-- LICENSE.txt
-- README.md
 - Rakefile
 - bin/console
 - bin/namespace_engine
 - bin/setup
 - lib/rails_namespace_engine.rb
 - lib/rails_namespace_engine/version.rb
+- rails_namespace_engine-0.1.0.gem
 - rails_namespace_engine.gemspec
-homepage: http://m.ller.io
+homepage: https://github.com/nathaniel-miller/namespace_engine/
 licenses:
 - MIT
 metadata:

data/CODE_OF_CONDUCT.md

@@ -1,74 +0,0 @@
-# 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 dukeoflaser@gmail.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/LICENSE.txt

@@ -1,21 +0,0 @@
-The MIT License (MIT)
-
-Copyright (c) 2017 TODO: Write your name
-
-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

@@ -1,41 +0,0 @@
-# RailsNamespaceEngine
-
-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/rails_namespace_engine`. 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 'rails_namespace_engine'
-```
-
-And then execute:
-
-    $ bundle
-
-Or install it yourself as:
-
-    $ gem install rails_namespace_engine
-
-## Usage
-
-TODO: Write usage instructions here
-
-## Development
-
-After checking out the repo, run `bin/setup` to install dependencies. 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/nathaniel-miller/rails_namespace_engine. 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](http://opensource.org/licenses/MIT).
-