linter 0.1.9 → 0.1.14

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a80c5734dad74a7737293169a71422fc05f45e75662615ee1b135e4efd96332e
-  data.tar.gz: cadc9e3c07b8fde011e5a0688efc9d309082d7a0f587a8d6ef616da25c3bd311
+  metadata.gz: 490ca0a35010f9adf558a5614e63497506e5353cace1b7f03b0dcbf69bec51e1
+  data.tar.gz: 7c330a8051749ff8933c903bc5e7c35f3c4b1a3a038983fe93a295f9b7e45997
 SHA512:
-  metadata.gz: b36c820823c1e67f49ce474ad589665d4e98fe4c8256656ede53b203de79137a1749e1c9d5acabf056d923b3c1db02d663bfdb075bf403656eb757d15b9e849e
-  data.tar.gz: 360c60b81bf244368b9a9e5421b641c3bd34d16436b252342aadd64c85eeae39601ccc3d44f0efe03521aa8db23770b5ee4722e75293f78b0a1639993507a9cd
+  metadata.gz: 5ae3017629e7201410ce6b8a5650553f6f2bf9d384a75a1c6581cc0922cf7e15cc41f54045f051ccc6ac55b8acdffe0b5e2807af1f06ea93074d851532d06dfa
+  data.tar.gz: cb66960cf4a7c51e843d1c00bdfb8ae90c45482b0574aa187065a9fd6cd941eb9595d8a89e13317831073bfccb85bbdee4784ea2b8a878389de0fa329f263c7a

data/README.md

@@ -30,6 +30,13 @@ text = 'your text here'
 response = Linter.analyze(text)
 ```
 
+If you want to include the checks specifically for job ads as well, run it like this:
+
+```ruby
+text = 'your text here'
+response = Linter.analyze(text, job_ad: true)
+```
+
 You can also use the checks individually:
 
 ```ruby
@@ -47,13 +54,15 @@ Linter::MisusedWords.analyze(text)
 ```
 
 You'll notice that the `association` checks do a comparison of the whole text and will determine a _trend_ for your text. When your text uses a lot of
-masculine-coded language, the text will be marked as such. The regular checks (like `MisusedWords`) will return all the misused words, a reason why
-and if possible, we provide some suggestions to replace the word.
+masculine-coded language, the text will be marked as such. The regular checks (like `MisusedWords`) will return all the misused words, a reason why and if possible, we provide some suggestions to replace the word.
+
+We've also included a `recommendation` where possible. This is to help guide people what to do with the results from the
+trend.
 
-## CLI Usage -> In development
+## CLI Usage
 
 ```console
-linter example.md
+linter path/to_file/example.md
 #<OpenStruct feminine_coded_word_counts={}, masculine_coded_word_counts={"analytical"=>1}, trend="strongly masculine-coded">
 #<OpenStruct feminine_coded_word_counts={}, masculine_coded_word_counts={"he"=>1}, trend="masculine-coded">
 ```
@@ -74,6 +83,8 @@ We are looking for different types of contributions:
 - support for other languages besides English
 - ...
 
+If you add any checks or words, please also add the sources used to the `sources.yml` file.
+
 ## License
 
 The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).

data/data/gender_association_wordlist.yml

@@ -7,6 +7,7 @@ words:
     - collab
     - commit
     - communal
+    - community
     - compassion
     - connect
     - considerate
@@ -33,6 +34,7 @@ words:
     - nurtur
     - pleasant
     - polite
+    - provide
     - quiet*
     - respon
     - sensitiv
@@ -73,6 +75,7 @@ words:
     - decisive
     - defend
     - determin
+    - direct
     - domina
     - dominant
     - driven
@@ -109,5 +112,6 @@ words:
     - selfrelian
     - selfsufficien
     - stubborn
+    - strong
     - superior
     - unreasonab

data/data/mindset_wordlist.yml

@@ -2,25 +2,30 @@ words:
   growth_coded:
     - striving
     - driven
+    - commit
     - highly motivated
-    - improvement
+    - improve
     - learn
     - strive
+    - serve
     - grow
-    - persevere
-    - determined
+    - persever
+    - determin
 
   fixed_coded:
+    - ability
     - est
-    - brightest
+    - bright
     - smart
     - performer
-    - intelligent
+    - intelligen
     - rockstar
     - superhero
     - genius
     - expert
+    - strong
+    - take
     - brilliant
     - natural
     - talent
-    - overachieve
+    - overachiev

data/data/recommendations.yml

@@ -0,0 +1,53 @@
+  - type: gender
+    trends:
+      - result: neutral
+        recommendation: |
+          Either you aren't using any gender-coded words or you found a good balance between using gender-coded words.
+          There could still be other factors that make this text less inclusive.
+      - result: masculine-coded
+        recommendation: |
+          You're using more masculine-coded words than feminine coded-words. Try to replace some of the words listed as masculine-coded.
+          This will result in a more balanced and inclusive text. If this happens to be a job ad, note that according to
+          <a href='http://gender-decoder.katmatfield.com/static/documents/Gaucher-Friesen-Kay-JPSP-Gendered-Wording-in-Job-ads.pdf'>this study</a>
+          it risks putting women off and encourage men to apply.
+      - result: strongly masculine-coded
+        recommendation: |
+          You're using more masculine-coded words than feminine coded-words. Try to replace some of the words listed as masculine-coded.
+          This will result in a more balanced and inclusive text. If this happens to be a job ad, note that according to
+          <a href='http://gender-decoder.katmatfield.com/static/documents/Gaucher-Friesen-Kay-JPSP-Gendered-Wording-in-Job-ads.pdf'>this study</a>
+          it risks putting women off and encourage men to apply.
+      - result: feminine-coded
+        recommendation: |
+          You're using more feminine coded-words than masculine-coded. You could replace some words however, a feminine-coded text only
+          has a slight effect on the inclusiveness of your text. For example, if this is a job ad, it will encourage women to apply
+          but the effect on men is minimal. See <a href='http://gender-decoder.katmatfield.com/static/documents/Gaucher-Friesen-Kay-JPSP-Gendered-Wording-in-Job-ads.pdf'>this study</a>.
+      - result: strongly feminine-coded
+        recommendation: |
+          You're using more feminine coded-words than masculine-coded. You could replace some words however, a feminine-coded text only
+          has a slight effect on the inclusiveness of your text. For example, if this is a job ad, it will encourage women to apply
+          but the effect on men is minimal. See <a href='http://gender-decoder.katmatfield.com/static/documents/Gaucher-Friesen-Kay-JPSP-Gendered-Wording-in-Job-ads.pdf'>this study</a>.
+  - type: mindset
+    trends:
+      - result: neutral
+        recommendation: |
+          Although it is marked as neutral, it might be good to look into changing the text a little bit. Growth mindset terms imply abilities and
+          talents can be developed. Recruiting content that uses growth mindset language can lead to faster hiring times
+          and more hires being made from underrepresented groups.
+      - result: growth-coded
+        recommendation: |
+          Growth mindset terms imply abilities and talents can be developed. Recruiting content that uses growth mindset language can lead to faster hiring times
+          and more hires being made from underrepresented groups. This text is a great start to make sure you're inclusive on a mindset-level.
+      - result: fixed-coded
+        recommendation: |
+          Fixed-mindset implies that talents and traits are innate and static. Recruiting content that uses growth mindset language can lead to faster hiring times
+          and more hires being made from underrepresented groups. We'd recommend you replace some of the words listed as fixed. You can find some more
+          information in <a href='https://medium.com/textio/growth-mindset-language-41d51c91432'>this medium post</a>.
+      - result: strongly growth-coded
+        recommendation: |
+          Growth mindset terms imply abilities and talents can be developed. Recruiting content that uses growth mindset language can lead to faster hiring times
+          and more hires being made from underrepresented groups. This text is a great start to make sure you're inclusive on a mindset-level.
+      - result: strongly fixed-coded
+        recommendation: |
+          Fixed-mindset implies that talents and traits are innate and static. Recruiting content that uses growth mindset language can lead to faster hiring times
+          and more hires being made from underrepresented groups. We'd recommend you replace some of the words listed as fixed. You can find some more
+          information in <a href='https://medium.com/textio/growth-mindset-language-41d51c91432'>this medium post</a>.

data/data/sources.yml

@@ -0,0 +1,7 @@
+# List any source used here. We will make sure this is listed and credit is given.
+- title: Gender Decoder Tool by Kat Matfield
+  url: http://gender-decoder.katmatfield.com/
+- title: Evidence That Gendered Wording in Job Advertisements Exists and Sustains Gender Inequality
+  url: http://gender-decoder.katmatfield.com/static/documents/Gaucher-Friesen-Kay-JPSP-Gendered-Wording-in-Job-ads.pdf
+- title: Want to hire faster? Write about “learning,” not “brilliance”
+  url: https://medium.com/textio/growth-mindset-language-41d51c91432

data/lib/linter.rb

@@ -16,12 +16,19 @@ module Linter
   class Error < StandardError; end
 
   class << self
-    def analyze(text)
-      {
+    def analyze(text, job_ad: false)
+      response = {
         gender_association_analysis: Linter::GenderAssociation.analyze(text),
         pronoun_analysis: Linter::PronounAssociation.analyze(text),
         misused_words_analysis: Linter::MisusedWords.analyze(text)
       }
+      response[:mindset_association_analysis] = Linter::MindsetAssociation.analyze(text) if job_ad
+      response
+    end
+
+    def sources
+      file_path = File.join(__dir__, '../data/sources.yml')
+      YAML.load_file(file_path)
     end
   end
 end

data/lib/linter/base_association.rb

@@ -2,6 +2,8 @@
 
 module Linter
   class BaseAssociation
+    SKIP_WORDS = ['directory'].freeze
+
     def self.analyze(text)
       result = OpenStruct.new(trend: '')
 
@@ -14,6 +16,7 @@ module Linter
       end
 
       result.trend = calculate_trend(result)
+      result.recommendation = add_recommendation(result)
       result
     end
 
@@ -30,9 +33,19 @@ module Linter
       matches
         .flatten
         .map(&:downcase)
+        .reject { |m| SKIP_WORDS.include? m}
         .group_by { |v| v }
         .transform_values(&:size)
         .to_h
     end
+
+    def self.recommendation_file
+      file_path = File.join(__dir__, '../../data/recommendations.yml')
+      @recommendation_file ||= YAML.load_file(file_path)
+    end
+
+    def self.add_recommendation(_result)
+      false
+    end
   end
 end

data/lib/linter/gender_association.rb

@@ -25,5 +25,9 @@ module Linter
         'masculine-coded'
       end
     end
+
+    def self.add_recommendation(result)
+      recommendation_file.find { |rec| rec['type'] == 'gender' }&.dig('trends')&.find { |trend| trend['result'] == result.trend }&.dig('recommendation')
+    end
   end
 end

data/lib/linter/mindset_association.rb

@@ -24,5 +24,9 @@ module Linter
         'fixed-coded'
       end
     end
+
+    def self.add_recommendation(result)
+      recommendation_file.find { |rec| rec['type'] == 'mindset' }&.dig('trends')&.find { |trend| trend['result'] == result.trend }&.dig('recommendation')
+    end
   end
 end

data/lib/linter/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Linter
-  VERSION = '0.1.9'
+  VERSION = '0.1.14'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: linter
 version: !ruby/object:Gem::Version
-  version: 0.1.9
+  version: 0.1.14
 platform: ruby
 authors:
 - lien van den steen
-autorequire: 
-bindir: exe
+autorequire:
+bindir: bin
 cert_chain: []
-date: 2020-06-16 00:00:00.000000000 Z
+date: 2020-08-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -16,14 +16,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.17'
+        version: '2.1'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.17'
+        version: '2.1'
 - !ruby/object:Gem::Dependency
   name: pry
   requirement: !ruby/object:Gem::Requirement
@@ -44,14 +44,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '10.0'
+        version: '13.0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '10.0'
+        version: '13.0'
 - !ruby/object:Gem::Dependency
   name: rspec
   requirement: !ruby/object:Gem::Requirement
@@ -80,6 +80,20 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '0.85'
+- !ruby/object:Gem::Dependency
+  name: rubocop-packaging
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.1'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.1'
 - !ruby/object:Gem::Dependency
   name: rubocop-rspec
   requirement: !ruby/object:Gem::Requirement
@@ -108,33 +122,23 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '0.8'
-description: 
+description:
 email:
 - lienvandensteen@gmail.com
-executables: []
+executables:
+- linter
 extensions: []
 extra_rdoc_files: []
 files:
-- ".gitignore"
-- ".gitlab-ci.yml"
-- ".rspec"
-- ".rubocop.yml"
-- ".rubocop_todo.yml"
-- ".ruby-version"
-- ".travis.yml"
-- CODE_OF_CONDUCT.md
-- Gemfile
-- Gemfile.lock
 - LICENSE.txt
 - README.md
-- Rakefile
-- bin/console
 - bin/linter
-- bin/setup
 - data/gender_association_wordlist.yml
 - data/mindset_wordlist.yml
 - data/misused_wordlist.yml
 - data/pronoun_association_wordlist.yml
+- data/recommendations.yml
+- data/sources.yml
 - lib/linter.rb
 - lib/linter/base_association.rb
 - lib/linter/cli.rb
@@ -143,14 +147,13 @@ files:
 - lib/linter/misused_words.rb
 - lib/linter/pronoun_association.rb
 - lib/linter/version.rb
-- linter.gemspec
 homepage: https://gitlab.com/lienvdsteen/linter
 licenses:
 - MIT
 metadata:
   homepage_uri: https://gitlab.com/lienvdsteen/linter
   source_code_uri: https://gitlab.com/lienvdsteen/linter
-post_install_message: 
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -166,7 +169,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubygems_version: 3.0.3
-signing_key: 
+signing_key:
 specification_version: 4
 summary: Library to check a text for gender coded language
 test_files: []

data/.gitignore

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

data/.gitlab-ci.yml

@@ -1,18 +0,0 @@
-rspec:
-  stage: test
-  only:
-    - merge_requests
-  script:
-    - bundle install
-    - bundle exec rspec
-
-rubocop:
-  stage: test
-  only:
-    - merge_requests
-  script:
-    - bundle install
-    - bundle exec rubocop
-
-include:
-  template: Dependency-Scanning.gitlab-ci.yml

data/.rspec

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

data/.rubocop.yml

@@ -1,70 +0,0 @@
-inherit_from: .rubocop_todo.yml
-
-require:
-  - rubocop-rspec
-AllCops:
-  TargetRubyVersion: 2.6
-  # Cop names are displayed in offense messages by default. Change behavior
-  # by overriding DisplayCopNames, or by giving the `--no-display-cop-names`
-  # option.
-  DisplayCopNames: true
-  # Style guide URLs are not displayed in offense messages by default. Change
-  # behavior by overriding DisplayStyleGuide, or by giving the
-  # -S/--display-style-guide option.
-  DisplayStyleGuide: false
-  # Exclude some GitLab files
-  Exclude:
-    - '.gitlab/**/*'
-
-Style/NumericLiteralPrefix:
-  Enabled: false
-Metrics/BlockLength:
-  Enabled: false
-Layout/LineLength:
-  Enabled: false
-Style/Documentation:
-  Enabled: false
-RSpec/FilePath:
-  Enabled: false
-Metrics/AbcSize:
-  Max: 60
-Metrics/MethodLength:
-  Max: 30
-RSpec/ExampleLength:
-  Enabled: false
-RSpec/MultipleExpectations:
-  Max: 2
-RSpec/NestedGroups:
-  Max: 5
-Layout/SpaceInsideHashLiteralBraces:
-  Enabled: false
-Layout/EmptyLinesAroundAttributeAccessor:
-  Enabled: true
-Layout/SpaceAroundMethodCallOperator:
-  Enabled: true
-Layout/SpaceInsideBlockBraces:
-  Enabled: false
-Style/SlicingWithRange:
-  Enabled: true
-Style/ConditionalAssignment:
-  EnforcedStyle: assign_inside_condition
-Lint/DeprecatedOpenSSLConstant:
-  Enabled: true
-Lint/MixedRegexpCaptureTypes:
-  Enabled: true
-Lint/RaiseException:
-  Enabled: true
-Lint/StructNewOverride:
-  Enabled: true
-Style/ExponentialNotation:
-  Enabled: true
-Style/HashEachMethods:
-  Enabled: true
-Style/HashTransformKeys:
-  Enabled: true
-Style/HashTransformValues:
-  Enabled: true
-Style/RedundantRegexpCharacterClass:
-  Enabled: true
-Style/RedundantRegexpEscape:
-  Enabled: true

data/.rubocop_todo.yml

@@ -1,60 +0,0 @@
-# This configuration was generated by
-# `rubocop --auto-gen-config`
-# on 2020-06-06 22:58:53 +0200 using RuboCop version 0.85.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
-# Cop supports --auto-correct.
-# Configuration parameters: AllowForAlignment, AllowBeforeTrailingComments, ForceEqualSignAlignment.
-Layout/ExtraSpacing:
-  Exclude:
-    - 'linter.gemspec'
-
-# Offense count: 3
-# Cop supports --auto-correct.
-Layout/SpaceAfterComma:
-  Exclude:
-    - 'lib/linter/gender_association.rb'
-    - 'lib/linter/misused_words.rb'
-    - 'lib/linter/pronoun_association.rb'
-
-# Offense count: 1
-# Cop supports --auto-correct.
-# Configuration parameters: AllowForAlignment, EnforcedStyleForExponentOperator.
-# SupportedStylesForExponentOperator: space, no_space
-Layout/SpaceAroundOperators:
-  Exclude:
-    - 'linter.gemspec'
-
-# Offense count: 4
-Lint/IneffectiveAccessModifier:
-  Exclude:
-    - 'lib/linter/gender_association.rb'
-    - 'lib/linter/misused_words.rb'
-    - 'lib/linter/pronoun_association.rb'
-
-# Offense count: 3
-# Cop supports --auto-correct.
-# Configuration parameters: ContextCreatingMethods, MethodCreatingMethods.
-Lint/UselessAccessModifier:
-  Exclude:
-    - 'lib/linter/gender_association.rb'
-    - 'lib/linter/misused_words.rb'
-    - 'lib/linter/pronoun_association.rb'
-
-# Offense count: 2
-# Cop supports --auto-correct.
-Style/ExpandPathArguments:
-  Exclude:
-    - 'linter.gemspec'
-
-# Offense count: 1
-# Cop supports --auto-correct.
-# Configuration parameters: EnforcedStyle.
-# SupportedStyles: always, always_true, never
-Style/FrozenStringLiteralComment:
-  Exclude:
-    - 'linter.gemspec'

data/.ruby-version

@@ -1 +0,0 @@
-2.6.5

data/.travis.yml

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

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 lienvandensteen@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/Gemfile

@@ -1,11 +0,0 @@
-# frozen_string_literal: true
-
-source 'https://rubygems.org'
-
-group :development do
-  gem 'pry'
-  gem 'rb-readline' # TODO: fix
-end
-
-# Specify your gem's dependencies in linter.gemspec
-gemspec

data/Gemfile.lock

@@ -1,69 +0,0 @@
-PATH
-  remote: .
-  specs:
-    linter (0.1.9)
-      colorize (~> 0.8)
-
-GEM
-  remote: https://rubygems.org/
-  specs:
-    ast (2.4.0)
-    coderay (1.1.3)
-    colorize (0.8.1)
-    diff-lcs (1.3)
-    method_source (1.0.0)
-    parallel (1.19.1)
-    parser (2.7.1.3)
-      ast (~> 2.4.0)
-    pry (0.13.1)
-      coderay (~> 1.1)
-      method_source (~> 1.0)
-    rainbow (3.0.0)
-    rake (10.5.0)
-    rb-readline (0.5.5)
-    regexp_parser (1.7.0)
-    rexml (3.2.4)
-    rspec (3.9.0)
-      rspec-core (~> 3.9.0)
-      rspec-expectations (~> 3.9.0)
-      rspec-mocks (~> 3.9.0)
-    rspec-core (3.9.2)
-      rspec-support (~> 3.9.3)
-    rspec-expectations (3.9.2)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.9.0)
-    rspec-mocks (3.9.1)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.9.0)
-    rspec-support (3.9.3)
-    rubocop (0.85.0)
-      parallel (~> 1.10)
-      parser (>= 2.7.0.1)
-      rainbow (>= 2.2.2, < 4.0)
-      regexp_parser (>= 1.7)
-      rexml
-      rubocop-ast (>= 0.0.3)
-      ruby-progressbar (~> 1.7)
-      unicode-display_width (>= 1.4.0, < 2.0)
-    rubocop-ast (0.0.3)
-      parser (>= 2.7.0.1)
-    rubocop-rspec (1.39.0)
-      rubocop (>= 0.68.1)
-    ruby-progressbar (1.10.1)
-    unicode-display_width (1.7.0)
-
-PLATFORMS
-  ruby
-
-DEPENDENCIES
-  bundler (~> 1.17)
-  linter!
-  pry
-  rake (~> 10.0)
-  rb-readline
-  rspec (~> 3.0)
-  rubocop (~> 0.85)
-  rubocop-rspec (~> 1.39)
-
-BUNDLED WITH
-   1.17.2

data/Rakefile

@@ -1,8 +0,0 @@
-# frozen_string_literal: true
-
-require 'bundler/gem_tasks'
-require 'rspec/core/rake_task'
-
-RSpec::Core::RakeTask.new(:spec)
-
-task default: :spec

data/bin/console

@@ -1,16 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-require 'bundler/setup'
-require 'linter'
-require 'pry'
-
-# 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

@@ -1,8 +0,0 @@
-#!/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/linter.gemspec

@@ -1,47 +0,0 @@
-lib = File.expand_path('../lib', __FILE__)
-$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
-require 'linter/version'
-
-Gem::Specification.new do |spec|
-  spec.name          = 'linter'
-  spec.version       = Linter::VERSION
-  spec.authors       = ['lien van den steen']
-  spec.email         = ['lienvandensteen@gmail.com']
-
-  spec.summary       = 'Library to check a text for gender coded language'
-  # spec.description   = %q{TODO: Write a longer description or delete this line.}
-  spec.homepage      = 'https://gitlab.com/lienvdsteen/linter'
-  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"
-
-    spec.metadata['homepage_uri'] = 'https://gitlab.com/lienvdsteen/linter'
-    spec.metadata['source_code_uri'] = 'https://gitlab.com/lienvdsteen/linter'
-    # spec.metadata['changelog_uri'] = 'TODO: Put your gem's CHANGELOG.md URL here.'
-  else
-    raise 'RubyGems 2.0 or newer is required to protect against ' \
-      'public gem pushes.'
-  end
-
-  # 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.
-  # Use expand_path(__dir__) instead of expand_path('..', __FILE__).
-  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 'bundler', '~> 1.17'
-  spec.add_development_dependency 'pry', '~> 0.13'
-  spec.add_development_dependency 'rake', '~> 10.0'
-  spec.add_development_dependency 'rspec', '~> 3.0'
-  spec.add_development_dependency 'rubocop', '~> 0.85'
-  spec.add_development_dependency 'rubocop-rspec', '~> 1.39'
-
-  spec.add_dependency('colorize', '~> 0.8')
-end