mense 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 819a5059e9a7439d094e1cc66e930d76b5a4ca3c0fbf1dfb662521538100e617
+  data.tar.gz: c5df2c69229224d40c1d814226dc00fff6edaab982743b3920ec84a4e93fb8f6
+SHA512:
+  metadata.gz: f9f4e74742b80d5116d67f1b3f673acb9aca752efb6ec35327aba63cc6a6d34a9da162158176f11fdccc4e35c246ce44a0de954d76bb85698aee3426457e1841
+  data.tar.gz: 5561c22920b0953024bfd6644c9cebc37a0e7362a5139bdb0862d0ab351b33e461bfe9022497654e42cc1484936f7e86ed5f3cb82315b0745724cd5d29233a2f

data/.devcontainer/devcontainer.json

@@ -0,0 +1,40 @@
+// See https://code.visualstudio.com/docs/remote/containers#_devcontainerjson-reference
+{
+  // General ===================================================================
+  // A display name for the container.
+  "name": "Mense",
+  // A command string or list of command arguments to run after the container is
+  // created. The commands execute from the workspaceFolder in the container.
+  // Use && in a string to execute multiple commands. For example,
+  // "yarn install" or "apt-get update && apt-get install -y git". The array
+  // syntax ["yarn", "install"] will invoke the command (in this case yarn)
+  // directly without using a shell.
+  //
+  // It fires after your source code has been mounted, so you can also run shell
+  // scripts from your source tree. For example:
+  // bash scripts/install-dev-tools.sh. Not set by default.
+  // "postCreateCommand": "dev-entrypoint.sh check-node-modules-owner",
+  // Dockerfile Compose Config =================================================
+  // Required. Path or an ordered list of paths to Docker Compose files relative
+  // to the devcontainer.json file. Using an array is useful when extending your
+  // Docker Compose configuration. The order of the array matters since the
+  // contents of later files can override values set in previous ones.
+  "dockerComposeFile": [
+    "../docker-compose.yml" // The compose file with the common services
+  ],
+  "shutdownAction": "stopCompose",
+  // Required. The name of the service VS Code should connect to once running.
+  "service": "app",
+  "workspaceFolder": "/workspaces/mense",
+  // An array of extension IDs that specify the extensions to install inside the
+  // container when you first attach to it.
+  "extensions": [
+    "dbaeumer.vscode-eslint",
+    "rebornix.ruby",
+    "castwide.solargraph",
+    "miguel-savignano.ruby-symbols",
+    "redhat.vscode-xml",
+    "eamodio.gitlens",
+    "github.vscode-pull-request-github",
+  ]
+}

data/.dockerignore

@@ -0,0 +1,27 @@
+# Ignore version control files:
+.git/
+.gitignore
+
+# Ignore github templates:
+.github/
+
+# Ignore docker and environment files:
+*Dockerfile
+docker-compose*.yml
+**/*.env
+.dockerignore
+
+# Ignore OS artifacts:
+**/.DS_Store
+**/.Identifier
+
+
+# 3: Ignore Development container's Home artifacts:
+# 3.1: Ignore bash / IRB / Byebug history files
+.*_hist*
+
+# 3.3: bundler stuff
+.bundle/*
+
+# 3.4: Codeclimate stuff:
+.rubocop.yml

data/.github/workflows/main.yml

@@ -0,0 +1,18 @@
+name: Ruby
+
+on: [push,pull_request]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v2
+    - name: Set up Ruby
+      uses: ruby/setup-ruby@v1
+      with:
+        ruby-version: 2.7.2
+    - name: Run the default task
+      run: |
+        gem install bundler -v 2.2.15
+        bundle install
+        bundle exec rake

data/.gitignore

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

data/.rspec

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

data/.rubocop.yml

@@ -0,0 +1,13 @@
+AllCops:
+  TargetRubyVersion: 2.4
+
+Style/StringLiterals:
+  Enabled: true
+  EnforcedStyle: double_quotes
+
+Style/StringLiteralsInInterpolation:
+  Enabled: true
+  EnforcedStyle: double_quotes
+
+Layout/LineLength:
+  Max: 120

data/CHANGELOG.md

@@ -0,0 +1,5 @@
+## [Unreleased]
+
+## [0.1.0] - 2021-11-23
+
+- Initial release

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders 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, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at kurenn@icalialabs.com. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

data/Dockerfile

@@ -0,0 +1,91 @@
+# Stage 1: Runtime =============================================================
+# The minimal package dependencies required to run the app in the release image:
+
+# Use the official Ruby 3.0.2 Slim Buster image as base:
+FROM ruby:3.0.2-slim-buster
+
+# We'll set MALLOC_ARENA_MAX for optimization purposes & prevent memory bloat
+# https://www.speedshop.co/2017/12/04/malloc-doubles-ruby-memory.html
+ENV MALLOC_ARENA_MAX="2"
+
+# Install the app build system dependency packages:
+RUN apt-get update \
+ && apt-get install -y --no-install-recommends \
+    build-essential \
+    git
+
+# Receive the developer user's UID and USER:
+ARG DEVELOPER_UID=1000
+ARG DEVELOPER_USERNAME=you
+
+# Replicate the developer user in the development image:
+RUN addgroup --gid ${DEVELOPER_UID} ${DEVELOPER_USERNAME} \
+ ;  useradd -r -m -u ${DEVELOPER_UID} --gid ${DEVELOPER_UID} \
+    --shell /bin/bash -c "Developer User,,," ${DEVELOPER_USERNAME}
+
+ # Ensure the developer user's home directory and app path are owned by him/her:
+# (A workaround to a side effect of setting WORKDIR before creating the user)
+RUN userhome=$(eval echo ~${DEVELOPER_USERNAME}) \
+ && chown -R ${DEVELOPER_USERNAME}:${DEVELOPER_USERNAME} $userhome \
+ && mkdir -p /workspaces/mense \
+ && chown -R ${DEVELOPER_USERNAME}:${DEVELOPER_USERNAME} /workspaces/mense
+
+# Set the app path as the working directory:
+WORKDIR /workspaces/mense
+
+# Change to the developer user:
+USER ${DEVELOPER_USERNAME}
+
+# Copy the project's Gemfile and Gemfile.lock files:
+COPY --chown=${DEVELOPER_USERNAME} Gemfile* /workspaces/mense/
+
+# Install the gems in the Gemfile, except for the ones in the "development"
+# group, which shouldn't be required in order to  run the tests with the leanest
+# Docker image possible:
+RUN bundle install --jobs=4 --retry=3
+
+# Receive the developer username again, as ARGS won't persist between stages on
+# non-buildkit builds:
+ARG DEVELOPER_USERNAME=you
+
+# Change to root user to install the development packages:
+USER root
+
+# Install sudo, along with any other tool required at development phase:
+RUN apt-get install -y --no-install-recommends \
+  # Adding bash autocompletion as git without autocomplete is a pain...
+  bash-completion \
+  # gpg & gpgconf is used to get Git Commit GPG Signatures working inside the
+  # VSCode devcontainer:
+  gpg \
+  openssh-client \
+  # Para esperar a que el servicio de minio (u otros) esté disponible:
+  netcat \
+  # /proc file system utilities: (watch, ps):
+  procps \
+  # Vim will be used to edit files when inside the container (git, etc):
+  vim \
+  # Sudo will be used to install/configure system stuff if needed during dev:
+  sudo
+
+# Add the developer user to the sudoers list:
+RUN echo "${DEVELOPER_USERNAME} ALL=(ALL) NOPASSWD:ALL" | tee "/etc/sudoers.d/${DEVELOPER_USERNAME}"
+
+# Persist the bash history between runs
+# - See https://code.visualstudio.com/docs/remote/containers-advanced#_persist-bash-history-between-runs
+RUN SNIPPET="export PROMPT_COMMAND='history -a' && export HISTFILE=/command-history/.bash_history" \
+ && mkdir /command-history \
+ && touch /command-history/.bash_history \
+ && chown -R ${DEVELOPER_USERNAME} /command-history \
+ && echo $SNIPPET >> "/home/${DEVELOPER_USERNAME}/.bashrc"
+
+ # Create the extensions directories:
+RUN mkdir -p \
+  /home/${DEVELOPER_USERNAME}/.vscode-server/extensions \
+  /home/${DEVELOPER_USERNAME}/.vscode-server-insiders/extensions \
+ && chown -R ${DEVELOPER_USERNAME} \
+  /home/${DEVELOPER_USERNAME}/.vscode-server \
+  /home/${DEVELOPER_USERNAME}/.vscode-server-insiders
+
+# Change back to the developer user:
+USER ${DEVELOPER_USERNAME}

data/Gemfile

@@ -0,0 +1,14 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+
+gem "rake", "~> 13.0"
+gem "rspec", "~> 3.0"
+gem "httparty"
+gem 'hashie'
+
+group :development do
+  gem "rubocop", "~> 1.7"
+  gem "solargraph"
+  gem 'pry'
+end

data/Gemfile.lock

@@ -0,0 +1,97 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    ast (2.4.2)
+    backport (1.2.0)
+    benchmark (0.2.0)
+    coderay (1.1.3)
+    diff-lcs (1.4.4)
+    e2mmap (0.1.0)
+    hashie (5.0.0)
+    httparty (0.20.0)
+      mime-types (~> 3.0)
+      multi_xml (>= 0.5.2)
+    jaro_winkler (1.5.4)
+    kramdown (2.3.1)
+      rexml
+    kramdown-parser-gfm (1.1.0)
+      kramdown (~> 2.0)
+    method_source (1.0.0)
+    mime-types (3.4.1)
+      mime-types-data (~> 3.2015)
+    mime-types-data (3.2021.1115)
+    multi_xml (0.6.0)
+    nokogiri (1.12.5-x86_64-linux)
+      racc (~> 1.4)
+    parallel (1.20.1)
+    parser (3.0.1.0)
+      ast (~> 2.4.1)
+    pry (0.14.1)
+      coderay (~> 1.1)
+      method_source (~> 1.0)
+    racc (1.6.0)
+    rainbow (3.0.0)
+    rake (13.0.3)
+    regexp_parser (2.1.1)
+    reverse_markdown (2.1.1)
+      nokogiri
+    rexml (3.2.5)
+    rspec (3.10.0)
+      rspec-core (~> 3.10.0)
+      rspec-expectations (~> 3.10.0)
+      rspec-mocks (~> 3.10.0)
+    rspec-core (3.10.1)
+      rspec-support (~> 3.10.0)
+    rspec-expectations (3.10.1)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.10.0)
+    rspec-mocks (3.10.2)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.10.0)
+    rspec-support (3.10.2)
+    rubocop (1.12.1)
+      parallel (~> 1.10)
+      parser (>= 3.0.0.0)
+      rainbow (>= 2.2.2, < 4.0)
+      regexp_parser (>= 1.8, < 3.0)
+      rexml
+      rubocop-ast (>= 1.2.0, < 2.0)
+      ruby-progressbar (~> 1.7)
+      unicode-display_width (>= 1.4.0, < 3.0)
+    rubocop-ast (1.4.1)
+      parser (>= 2.7.1.5)
+    ruby-progressbar (1.11.0)
+    solargraph (0.44.2)
+      backport (~> 1.2)
+      benchmark
+      bundler (>= 1.17.2)
+      diff-lcs (~> 1.4)
+      e2mmap
+      jaro_winkler (~> 1.5)
+      kramdown (~> 2.3)
+      kramdown-parser-gfm (~> 1.1)
+      parser (~> 3.0)
+      reverse_markdown (>= 1.0.5, < 3)
+      rubocop (>= 0.52)
+      thor (~> 1.0)
+      tilt (~> 2.0)
+      yard (~> 0.9, >= 0.9.24)
+    thor (1.1.0)
+    tilt (2.0.10)
+    unicode-display_width (2.0.0)
+    yard (0.9.26)
+
+PLATFORMS
+  x86_64-linux
+
+DEPENDENCIES
+  hashie
+  httparty
+  pry
+  rake (~> 13.0)
+  rspec (~> 3.0)
+  rubocop (~> 1.7)
+  solargraph
+
+BUNDLED WITH
+   2.2.22

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2021 Abraham Kuri
+
+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 @@
+# Mense
+
+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/mense`. 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 'mense'
+```
+
+And then execute:
+
+    $ bundle install
+
+Or install it yourself as:
+
+    $ gem install mense
+
+## 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 the created tag, 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]/mense. 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]/mense/blob/master/CODE_OF_CONDUCT.md).
+
+## 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 Mense project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/mense/blob/master/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -0,0 +1,10 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+require "rubocop/rake_task"
+
+task default: %i[spec]

data/bin/console

@@ -0,0 +1,19 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+require "bundler/setup"
+require_relative "../lib/mense"
+
+Mense.configure do |config|
+  config.api_key = ENV['PEOPLE_DATA_LABS_API_KEY']
+end
+
+# 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/docker-compose.yml

@@ -0,0 +1,35 @@
+version: "3.7"
+
+volumes:
+  gem_bundle:   # Used to store the app's gem libraries...
+
+services:
+  # The test container - we'll use this as the base for the rest
+  # of the app service definitions:
+  app: &app
+    build:
+      context: .
+      dockerfile: Dockerfile
+      args:
+        DEVELOPER_UID: ${UID:-1000}
+        DEVELOPER_USERNAME: ${USER:-you}
+    image: coba/mense:development
+    volumes:
+      # Mount the app code into the app containers:
+      - .:/workspaces/mense
+
+      # After mounting the app code, we will use volumes to store the project's
+      # gem libraries and node modules.
+
+      # In the case of the gem libraries, the "gem_bundle" volume will be
+      # initialized with the development image's installed gems. Gems can be
+      # added later during the development process without re-building the
+      # development image:
+      - gem_bundle:/usr/local/bundle
+    # Keep the stdin open, so we can attach to our app container's process
+    # and do things such as byebug, etc:
+    stdin_open: true
+
+    # Enable sending signals (CTRL+C, CTRL+P + CTRL+Q) into the container:
+    tty: true
+    env_file: .env

data/lib/mense/base.rb

@@ -0,0 +1,13 @@
+# frozen_string_literal: true
+
+require 'hashie'
+
+module Mense
+  class Base < Hash
+    include Hashie::Extensions::MergeInitializer
+    include Hashie::Extensions::IndifferentAccess
+    include Hashie::Extensions::MethodReader
+    include Hashie::Extensions::DeepMerge
+    include Hashie::Extensions::Coercion
+  end
+end

data/lib/mense/client.rb

@@ -0,0 +1,14 @@
+# frozen_string_literal: true
+
+require 'httparty'
+
+module Mense
+  module Client
+    def self.included(base)
+      base.include HTTParty
+
+      base.base_uri "https://api.peopledatalabs.com/v5"
+    end
+
+  end
+end

data/lib/mense/company.rb

@@ -0,0 +1,32 @@
+# frozen_string_literal: true
+
+module Mense
+  class Company < Mense::Base
+    class Location < Mense::Base; end
+
+    coerce_key :location, Mense::Company::Location
+
+    include Mense::Client
+
+    def self.enrich(params = {})
+      response = get('/company/enrich', query: params, headers: { "X-API-Key" => Mense.api_key,
+                                                                "Content-Type" => "application/json"})
+
+      self.new(response)
+    end
+
+    def self.clean(params = {})
+      response = get('/company/clean', query: params, headers: { "X-API-Key" => Mense.api_key,
+                                                                "Content-Type" => "application/json"})
+
+      self.new(response)
+    end
+
+    def self.search(params = {})
+      response = get("/company/search", query: params, headers: { "X-API-Key" => Mense.api_key,
+                                                                "Content-Type" => "application/json"})
+
+      response
+    end
+  end
+end

data/lib/mense/education.rb

@@ -0,0 +1,13 @@
+# frozen_string_literal: true
+
+module Mense
+  class Education < Mense::Base
+
+    class School < Mense::Base
+      class Location < Mense::Base; end
+      coerce_key :location, Location
+    end
+
+    coerce_key :school, School
+  end
+end

data/lib/mense/experience.rb

@@ -0,0 +1,13 @@
+# frozen_string_literal: true
+
+module Mense
+  class Experience < Mense::Base
+
+    class Company < Mense::Base
+      class Location < Mense::Base; end
+      coerce_key :location, Location
+    end
+
+    coerce_key :company, Company
+  end
+end

data/lib/mense/person.rb

@@ -0,0 +1,49 @@
+
+# frozen_string_literal: true
+
+require_relative 'experience'
+require_relative 'education'
+require_relative 'profile'
+
+module Mense
+  class Person < Mense::Base
+    class Email < Mense::Base; end
+
+    coerce_key :experience, Array[Mense::Experience]
+    coerce_key :education, Array[Mense::Education]
+    coerce_key :profiles, Array[Mense::Profile]
+    coerce_key :emails, Array[Mense::Person::Email]
+
+    include Mense::Client
+
+    attr_reader :likelihood
+
+    def initialize(attributes = {})
+      @likelihood = attributes["likelihood"]
+      super(attributes["data"])
+    end
+
+    def self.enrich(params = {})
+      response = get('/person/enrich', query: params, headers: { "X-API-Key" => Mense.api_key })
+
+      self.new(response)
+    end
+
+    def self.search(params = {})
+      response = get("/person/search", query: params, headers: { "X-API-Key" => Mense.api_key,
+                                                                "Content-Type" => "application/json"})
+
+      response
+    end
+
+    def self.retrieve(id, params = {})
+      response = get("/person/retrieve/#{id}", query: params, headers: { "X-API-Key" => Mense.api_key })
+
+      self.new(response)
+    end
+
+    class <<self
+      alias_method :find, :retrieve
+    end
+  end
+end

data/lib/mense/profile.rb

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+module Mense
+  class Profile < Mense::Base; end
+end

data/lib/mense/version.rb

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+module Mense
+  VERSION = "0.1.0"
+end

data/lib/mense.rb

@@ -0,0 +1,26 @@
+# frozen_string_literal: true
+
+require_relative "mense/version"
+
+module Mense
+
+  @@api_key = nil
+
+  def self.api_key=(api_key)
+    @@api_key = api_key
+  end
+
+  def self.api_key
+    @@api_key
+  end
+
+  def self.configure
+    yield self
+  end
+end
+
+require 'pry'
+require_relative 'mense/client'
+require_relative 'mense/base'
+require_relative 'mense/person'
+require_relative 'mense/company'

data/mense.gemspec

@@ -0,0 +1,39 @@
+# frozen_string_literal: true
+
+lib = File.expand_path('lib', __dir__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require_relative "lib/mense/version"
+
+Gem::Specification.new do |spec|
+  spec.name          = "mense"
+  spec.version       = Mense::VERSION
+  spec.authors       = ["Abraham Kuri"]
+  spec.email         = ["abkuri88@gmail.com"]
+
+  spec.summary       = "A wrapper for the People Data Labs API"
+  spec.description   = "A wrapper for the People Data Labs API"
+  spec.homepage      = "https://github.com/kurenn/mense"
+  spec.license       = "MIT"
+  spec.required_ruby_version = Gem::Requirement.new(">= 2.4.0")
+
+  spec.metadata["allowed_push_host"] = "https://rubygems.org"
+
+  spec.metadata["homepage_uri"] = spec.homepage
+  spec.metadata["source_code_uri"] = "https://github.com/kurenn/mense"
+  spec.metadata["changelog_uri"] = "https://github.com/kurenn/mense/blob/master/CHANGELOG.md"
+
+  # 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(__dir__)) do
+    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{\A(?:test|spec|features)/}) }
+  end
+  spec.bindir        = "exe"
+  spec.executables   = spec.files.grep(%r{\Aexe/}) { |f| File.basename(f) }
+  spec.require_paths = ["lib"]
+
+  # Uncomment to register a new dependency of your gem
+  # spec.add_dependency "example-gem", "~> 1.0"
+
+  # For more information and examples about making a new gem, checkout our
+  # guide at: https://bundler.io/guides/creating_gem.html
+end

metadata

@@ -0,0 +1,74 @@
+--- !ruby/object:Gem::Specification
+name: mense
+version: !ruby/object:Gem::Version
+  version: 0.1.0
+platform: ruby
+authors:
+- Abraham Kuri
+autorequire: 
+bindir: exe
+cert_chain: []
+date: 2021-11-25 00:00:00.000000000 Z
+dependencies: []
+description: A wrapper for the People Data Labs API
+email:
+- abkuri88@gmail.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".devcontainer/devcontainer.json"
+- ".dockerignore"
+- ".github/workflows/main.yml"
+- ".gitignore"
+- ".rspec"
+- ".rubocop.yml"
+- CHANGELOG.md
+- CODE_OF_CONDUCT.md
+- Dockerfile
+- Gemfile
+- Gemfile.lock
+- LICENSE.txt
+- README.md
+- Rakefile
+- bin/console
+- bin/setup
+- docker-compose.yml
+- lib/mense.rb
+- lib/mense/base.rb
+- lib/mense/client.rb
+- lib/mense/company.rb
+- lib/mense/education.rb
+- lib/mense/experience.rb
+- lib/mense/person.rb
+- lib/mense/profile.rb
+- lib/mense/version.rb
+- mense.gemspec
+homepage: https://github.com/kurenn/mense
+licenses:
+- MIT
+metadata:
+  allowed_push_host: https://rubygems.org
+  homepage_uri: https://github.com/kurenn/mense
+  source_code_uri: https://github.com/kurenn/mense
+  changelog_uri: https://github.com/kurenn/mense/blob/master/CHANGELOG.md
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: 2.4.0
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 3.2.22
+signing_key: 
+specification_version: 4
+summary: A wrapper for the People Data Labs API
+test_files: []