boring_generators 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +7 -0
- data/.gitignore +10 -0
- data/.travis.yml +6 -0
- data/CHANGELOG.md +10 -0
- data/CODE_OF_CONDUCT.md +74 -0
- data/CONTRIBUTING.md +20 -0
- data/Gemfile +7 -0
- data/LICENSE.txt +21 -0
- data/README.md +44 -0
- data/Rakefile +10 -0
- data/bin/console +14 -0
- data/bin/setup +8 -0
- data/boring_generators.gemspec +29 -0
- data/lib/boring_generators.rb +6 -0
- data/lib/boring_generators/version.rb +3 -0
- data/lib/generators/boring/tailwind/install/install_generator.rb +66 -0
- data/lib/generators/boring/tailwind/install/templates/application.scss +3 -0
- metadata +65 -0
checksums.yaml
ADDED
@@ -0,0 +1,7 @@
|
|
1
|
+
---
|
2
|
+
SHA256:
|
3
|
+
metadata.gz: fdb73c106d2605bd3f2a97cc509f2204dc7d74670f4b67685abebf01ea93e42a
|
4
|
+
data.tar.gz: dccbd9b93fd021b3fc4e8a567166d0d0134ddd4ec6a51251f3b4d18204ce6daf
|
5
|
+
SHA512:
|
6
|
+
metadata.gz: 2158a1c67c89389e4c17cd53df289bc623c47191253d2a4e9c1cb665e0c47ad0cf65ae92f290fbaf8a927028c150be8194ad8dc6e1a3f3744a56bc9d6168c290
|
7
|
+
data.tar.gz: c5b4082ae50708c0846aee643cd88fa9b7f40ed88766124f9eee86135f90b6e0a9e63760edce26d5dbe3748cf27b5794089b2c39ff3d6df5d891cf3eb82e19c6
|
data/.gitignore
ADDED
data/.travis.yml
ADDED
data/CHANGELOG.md
ADDED
data/CODE_OF_CONDUCT.md
ADDED
@@ -0,0 +1,74 @@
|
|
1
|
+
# Contributor Covenant Code of Conduct
|
2
|
+
|
3
|
+
## Our Pledge
|
4
|
+
|
5
|
+
In the interest of fostering an open and welcoming environment, we as
|
6
|
+
contributors and maintainers pledge to making participation in our project and
|
7
|
+
our community a harassment-free experience for everyone, regardless of age, body
|
8
|
+
size, disability, ethnicity, gender identity and expression, level of experience,
|
9
|
+
nationality, personal appearance, race, religion, or sexual identity and
|
10
|
+
orientation.
|
11
|
+
|
12
|
+
## Our Standards
|
13
|
+
|
14
|
+
Examples of behavior that contributes to creating a positive environment
|
15
|
+
include:
|
16
|
+
|
17
|
+
* Using welcoming and inclusive language
|
18
|
+
* Being respectful of differing viewpoints and experiences
|
19
|
+
* Gracefully accepting constructive criticism
|
20
|
+
* Focusing on what is best for the community
|
21
|
+
* Showing empathy towards other community members
|
22
|
+
|
23
|
+
Examples of unacceptable behavior by participants include:
|
24
|
+
|
25
|
+
* The use of sexualized language or imagery and unwelcome sexual attention or
|
26
|
+
advances
|
27
|
+
* Trolling, insulting/derogatory comments, and personal or political attacks
|
28
|
+
* Public or private harassment
|
29
|
+
* Publishing others' private information, such as a physical or electronic
|
30
|
+
address, without explicit permission
|
31
|
+
* Other conduct which could reasonably be considered inappropriate in a
|
32
|
+
professional setting
|
33
|
+
|
34
|
+
## Our Responsibilities
|
35
|
+
|
36
|
+
Project maintainers are responsible for clarifying the standards of acceptable
|
37
|
+
behavior and are expected to take appropriate and fair corrective action in
|
38
|
+
response to any instances of unacceptable behavior.
|
39
|
+
|
40
|
+
Project maintainers have the right and responsibility to remove, edit, or
|
41
|
+
reject comments, commits, code, wiki edits, issues, and other contributions
|
42
|
+
that are not aligned to this Code of Conduct, or to ban temporarily or
|
43
|
+
permanently any contributor for other behaviors that they deem inappropriate,
|
44
|
+
threatening, offensive, or harmful.
|
45
|
+
|
46
|
+
## Scope
|
47
|
+
|
48
|
+
This Code of Conduct applies both within project spaces and in public spaces
|
49
|
+
when an individual is representing the project or its community. Examples of
|
50
|
+
representing a project or community include using an official project e-mail
|
51
|
+
address, posting via an official social media account, or acting as an appointed
|
52
|
+
representative at an online or offline event. Representation of a project may be
|
53
|
+
further defined and clarified by project maintainers.
|
54
|
+
|
55
|
+
## Enforcement
|
56
|
+
|
57
|
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
58
|
+
reported by contacting the project team at nikam.abhay1@gmail.com. All
|
59
|
+
complaints will be reviewed and investigated and will result in a response that
|
60
|
+
is deemed necessary and appropriate to the circumstances. The project team is
|
61
|
+
obligated to maintain confidentiality with regard to the reporter of an incident.
|
62
|
+
Further details of specific enforcement policies may be posted separately.
|
63
|
+
|
64
|
+
Project maintainers who do not follow or enforce the Code of Conduct in good
|
65
|
+
faith may face temporary or permanent repercussions as determined by other
|
66
|
+
members of the project's leadership.
|
67
|
+
|
68
|
+
## Attribution
|
69
|
+
|
70
|
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
|
71
|
+
available at [https://contributor-covenant.org/version/1/4][version]
|
72
|
+
|
73
|
+
[homepage]: https://contributor-covenant.org
|
74
|
+
[version]: https://contributor-covenant.org/version/1/4/
|
data/CONTRIBUTING.md
ADDED
@@ -0,0 +1,20 @@
|
|
1
|
+
# Contributing
|
2
|
+
|
3
|
+
We love contributions from everyone. Please open a issue for discussion or raise a
|
4
|
+
pull request with the changes you need in the package.
|
5
|
+
|
6
|
+
## Contributing Code
|
7
|
+
To start contributing to the package. We should follow following steps.
|
8
|
+
|
9
|
+
- Fork the repository first to your GitHub account.
|
10
|
+
- Install all package dependencies by executing `bundle install` in your console.
|
11
|
+
- Add test cases for the changes made in the pull request. Make sure they are passing by running `rake test`.
|
12
|
+
- Update documentation for the changes made if needed.
|
13
|
+
- Add a changelog for the new feature or fixes.
|
14
|
+
|
15
|
+
Push to your fork. Write a [good commit message][commit]. Submit a pull request.
|
16
|
+
|
17
|
+
[commit]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
|
18
|
+
|
19
|
+
Please do not self reject your thoughts. Let's discuss even smallest feature request as well and make
|
20
|
+
this package better for everybody's use.
|
data/Gemfile
ADDED
data/LICENSE.txt
ADDED
@@ -0,0 +1,21 @@
|
|
1
|
+
The MIT License (MIT)
|
2
|
+
|
3
|
+
Copyright (c) 2020 Abhay Nikam
|
4
|
+
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
7
|
+
in the Software without restriction, including without limitation the rights
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
10
|
+
furnished to do so, subject to the following conditions:
|
11
|
+
|
12
|
+
The above copyright notice and this permission notice shall be included in
|
13
|
+
all copies or substantial portions of the Software.
|
14
|
+
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
21
|
+
THE SOFTWARE.
|
data/README.md
ADDED
@@ -0,0 +1,44 @@
|
|
1
|
+
# BoringGenerators
|
2
|
+
|
3
|
+
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/boring_generators`. To experiment with that code, run `bin/console` for an interactive prompt.
|
4
|
+
|
5
|
+
TODO: Delete this and the text above, and describe your gem
|
6
|
+
|
7
|
+
## Installation
|
8
|
+
|
9
|
+
Add this line to your application's Gemfile:
|
10
|
+
|
11
|
+
```ruby
|
12
|
+
gem 'boring_generators'
|
13
|
+
```
|
14
|
+
|
15
|
+
And then execute:
|
16
|
+
|
17
|
+
$ bundle install
|
18
|
+
|
19
|
+
Or install it yourself as:
|
20
|
+
|
21
|
+
$ gem install boring_generators
|
22
|
+
|
23
|
+
## Usage
|
24
|
+
|
25
|
+
TODO: Write usage instructions here
|
26
|
+
|
27
|
+
## Development
|
28
|
+
|
29
|
+
After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake test` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
|
30
|
+
|
31
|
+
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).
|
32
|
+
|
33
|
+
## Contributing
|
34
|
+
|
35
|
+
Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/boring_generators. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/[USERNAME]/boring_generators/blob/master/CODE_OF_CONDUCT.md).
|
36
|
+
|
37
|
+
|
38
|
+
## License
|
39
|
+
|
40
|
+
The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
|
41
|
+
|
42
|
+
## Code of Conduct
|
43
|
+
|
44
|
+
Everyone interacting in the BoringGenerators project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/boring_generators/blob/master/CODE_OF_CONDUCT.md).
|
data/Rakefile
ADDED
data/bin/console
ADDED
@@ -0,0 +1,14 @@
|
|
1
|
+
#!/usr/bin/env ruby
|
2
|
+
|
3
|
+
require "bundler/setup"
|
4
|
+
require "boring_generators"
|
5
|
+
|
6
|
+
# You can add fixtures and/or initialization code here to make experimenting
|
7
|
+
# with your gem easier. You can also use a different console, if you like.
|
8
|
+
|
9
|
+
# (If you use this, don't forget to add pry to your Gemfile!)
|
10
|
+
# require "pry"
|
11
|
+
# Pry.start
|
12
|
+
|
13
|
+
require "irb"
|
14
|
+
IRB.start(__FILE__)
|
data/bin/setup
ADDED
@@ -0,0 +1,29 @@
|
|
1
|
+
require_relative 'lib/boring_generators/version'
|
2
|
+
|
3
|
+
Gem::Specification.new do |spec|
|
4
|
+
spec.name = "boring_generators"
|
5
|
+
spec.version = BoringGenerators::VERSION
|
6
|
+
spec.authors = ["Abhay Nikam"]
|
7
|
+
spec.email = ["nikam.abhay1@gmail.com"]
|
8
|
+
|
9
|
+
spec.summary = %q{Boring generators aims to make your development faster by delegating boring setups to us.}
|
10
|
+
spec.description = %q{Every new project or hobby project of yours needs to setup simple things. Boring generators aims to make your development faster by delegating boring setups to us and let you worry about the core problems project intends to solve.}
|
11
|
+
spec.homepage = "https://github.com/abhaynikam/boring_generators"
|
12
|
+
spec.license = "MIT"
|
13
|
+
spec.required_ruby_version = Gem::Requirement.new(">= 2.3.0")
|
14
|
+
|
15
|
+
# spec.metadata["allowed_push_host"] = "TODO: Set to 'http://mygemserver.com'"
|
16
|
+
|
17
|
+
spec.metadata["homepage_uri"] = spec.homepage
|
18
|
+
spec.metadata["source_code_uri"] = "https://github.com/abhaynikam/boring-generators"
|
19
|
+
spec.metadata["changelog_uri"] = "https://github.com/abhaynikam/boring-generators."
|
20
|
+
|
21
|
+
# Specify which files should be added to the gem when it is released.
|
22
|
+
# The `git ls-files -z` loads the files in the RubyGem that have been added into git.
|
23
|
+
spec.files = Dir.chdir(File.expand_path('..', __FILE__)) do
|
24
|
+
`git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
|
25
|
+
end
|
26
|
+
spec.bindir = "exe"
|
27
|
+
spec.executables = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
|
28
|
+
spec.require_paths = ["lib"]
|
29
|
+
end
|
@@ -0,0 +1,66 @@
|
|
1
|
+
# frozen_string_literal: true
|
2
|
+
|
3
|
+
module Boring
|
4
|
+
module Tailwind
|
5
|
+
class InstallGenerator < Rails::Generators::Base
|
6
|
+
desc "Adds Tailwind CSS to the application"
|
7
|
+
source_root File.expand_path("templates", __dir__)
|
8
|
+
|
9
|
+
class_option :skip_tailwind_css_ui, type: :boolean, aliases: "-sui",
|
10
|
+
desc: "Skip adding @tailwindcss/ui package"
|
11
|
+
class_option :skip_tailwind_init_full, type: :boolean, aliases: "-sif",
|
12
|
+
desc: "Skip running tailwindcss init with --full option"
|
13
|
+
|
14
|
+
def add_tailwind_package
|
15
|
+
say "Adding tailwind package", :green
|
16
|
+
if options[:skip_tailwind_css_ui]
|
17
|
+
run "yarn add tailwindcss"
|
18
|
+
else
|
19
|
+
run "yarn add tailwindcss @tailwindcss/ui"
|
20
|
+
end
|
21
|
+
end
|
22
|
+
|
23
|
+
def create_tailwind_config
|
24
|
+
say "Initailizing tailwind configuration", :green
|
25
|
+
if options[:skip_tailwind_init_full]
|
26
|
+
run "yarn tailwindcss init"
|
27
|
+
else
|
28
|
+
run "yarn tailwindcss init --full"
|
29
|
+
end
|
30
|
+
end
|
31
|
+
|
32
|
+
def include_tailwind_to_postcss_config
|
33
|
+
insert_into_file "postcss.config.js", <<~RUBY, after: /plugins:\s+\[\n/
|
34
|
+
\t\trequire('tailwindcss'),
|
35
|
+
RUBY
|
36
|
+
end
|
37
|
+
|
38
|
+
def add_or_import_stylesheet_for_tailwind
|
39
|
+
if File.exist?("app/javascript/stylesheets/application.scss")
|
40
|
+
say "Add tailwindcss imports to the application.scss", :green
|
41
|
+
append_to_file "app/javascript/stylesheets/application.scss" do
|
42
|
+
'@import "tailwindcss/base";'
|
43
|
+
'@import "tailwindcss/components";'
|
44
|
+
'@import "tailwindcss/utilities";'
|
45
|
+
|
46
|
+
end
|
47
|
+
else
|
48
|
+
say "Copying application.scss with tailwind imports", :green
|
49
|
+
template("application.scss", "app/javascript/stylesheets/application.scss")
|
50
|
+
|
51
|
+
if File.exist?("app/javascript/packs/application.js")
|
52
|
+
append_to_file "app/javascript/packs/application.js" do
|
53
|
+
'import "stylesheets/application"'
|
54
|
+
end
|
55
|
+
else
|
56
|
+
raise "Looks like the webpacker installation is incomplete. Could not find application.js in app/javascript/packs."
|
57
|
+
end
|
58
|
+
|
59
|
+
insert_into_file "app/views/layouts/application.html.erb", <<~RUBY, after: /stylesheet_link_tag.*\n/
|
60
|
+
<%= stylesheet_pack_tag 'application', 'data-turbolinks-track': 'reload' %>
|
61
|
+
RUBY
|
62
|
+
end
|
63
|
+
end
|
64
|
+
end
|
65
|
+
end
|
66
|
+
end
|
metadata
ADDED
@@ -0,0 +1,65 @@
|
|
1
|
+
--- !ruby/object:Gem::Specification
|
2
|
+
name: boring_generators
|
3
|
+
version: !ruby/object:Gem::Version
|
4
|
+
version: 0.1.0
|
5
|
+
platform: ruby
|
6
|
+
authors:
|
7
|
+
- Abhay Nikam
|
8
|
+
autorequire:
|
9
|
+
bindir: exe
|
10
|
+
cert_chain: []
|
11
|
+
date: 2020-09-05 00:00:00.000000000 Z
|
12
|
+
dependencies: []
|
13
|
+
description: Every new project or hobby project of yours needs to setup simple things.
|
14
|
+
Boring generators aims to make your development faster by delegating boring setups
|
15
|
+
to us and let you worry about the core problems project intends to solve.
|
16
|
+
email:
|
17
|
+
- nikam.abhay1@gmail.com
|
18
|
+
executables: []
|
19
|
+
extensions: []
|
20
|
+
extra_rdoc_files: []
|
21
|
+
files:
|
22
|
+
- ".gitignore"
|
23
|
+
- ".travis.yml"
|
24
|
+
- CHANGELOG.md
|
25
|
+
- CODE_OF_CONDUCT.md
|
26
|
+
- CONTRIBUTING.md
|
27
|
+
- Gemfile
|
28
|
+
- LICENSE.txt
|
29
|
+
- README.md
|
30
|
+
- Rakefile
|
31
|
+
- bin/console
|
32
|
+
- bin/setup
|
33
|
+
- boring_generators.gemspec
|
34
|
+
- lib/boring_generators.rb
|
35
|
+
- lib/boring_generators/version.rb
|
36
|
+
- lib/generators/boring/tailwind/install/install_generator.rb
|
37
|
+
- lib/generators/boring/tailwind/install/templates/application.scss
|
38
|
+
homepage: https://github.com/abhaynikam/boring_generators
|
39
|
+
licenses:
|
40
|
+
- MIT
|
41
|
+
metadata:
|
42
|
+
homepage_uri: https://github.com/abhaynikam/boring_generators
|
43
|
+
source_code_uri: https://github.com/abhaynikam/boring-generators
|
44
|
+
changelog_uri: https://github.com/abhaynikam/boring-generators.
|
45
|
+
post_install_message:
|
46
|
+
rdoc_options: []
|
47
|
+
require_paths:
|
48
|
+
- lib
|
49
|
+
required_ruby_version: !ruby/object:Gem::Requirement
|
50
|
+
requirements:
|
51
|
+
- - ">="
|
52
|
+
- !ruby/object:Gem::Version
|
53
|
+
version: 2.3.0
|
54
|
+
required_rubygems_version: !ruby/object:Gem::Requirement
|
55
|
+
requirements:
|
56
|
+
- - ">="
|
57
|
+
- !ruby/object:Gem::Version
|
58
|
+
version: '0'
|
59
|
+
requirements: []
|
60
|
+
rubygems_version: 3.1.2
|
61
|
+
signing_key:
|
62
|
+
specification_version: 4
|
63
|
+
summary: Boring generators aims to make your development faster by delegating boring
|
64
|
+
setups to us.
|
65
|
+
test_files: []
|