minecraft-data 0.1.1 → 0.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: b01f69a3a7d15f06f46d81c2d7651e084c9cfe91ccf85e380c77ec40f450ffd3
-  data.tar.gz: 48a2b7bb4b91de47a30de0221e7de149e575dabf27a7ccc74a2e97db09f69d3b
+  metadata.gz: ea3560f24a206a8bc2892ee58b13dc6fa81feb55bcf07ebe10b4d86f8371c4a4
+  data.tar.gz: 313ffea36aa3078b5ba39d86b44843e931d03eb424ebcda037608979231ac7f4
 SHA512:
-  metadata.gz: b03970aafc4c51525d46d02ec7af3f0de7c3556a8a03939974609bd8d3eb4ee16a8937950e98576f6be82f52225090787d94cd8d9156efa33607d6bd0af6a90b
-  data.tar.gz: b33cb1306820313e5763e2c5475be0222ee7b03685e89c0d5cc8bee1d5be63c8d5a93f08e50644f83af82e000f21fca60963152116af959fe856e410ef34f6f2
+  metadata.gz: 8d99f0522fd38efc5688096e3472010adec925bf465948f85ab36b21411371023b6acd8093de96a89e5aeacc969ed9ed0910a672ce60bb0fee5df2c2f7f97722
+  data.tar.gz: f4f7098f4ba6cf388fe94c6db4a29bdb138b646d6a934d224a8948ae9cd9cc4a30ec2d7218ab1089c20fc50398e222d6f137ab127d4e0d36a0cd4a51bcab99cf

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    minecraft-data (0.1.0)
+    minecraft-data (0.1.1)
       json (~> 2.3)
       uuidtools (~> 2.1, >= 2.1.5)
 

data/README.md

@@ -2,7 +2,7 @@
 
 Minecraft Data is a dead simple ruby gem to gather different pieces of information related to Minecraft player profiles.
 
-Services:
+Services used:
   * https://github.com/Electroid/mojang-api - User data.
     * https://api.ashcon.app/mojang/v1/user/Notch
   * https://crafatar.com - Skin heads.
@@ -61,14 +61,14 @@ Output:
 Retrieves a link pointing to an image of the given user's skin head. `true` or `false` depending on whether you want the skin's overlay to be present or not.
 
 ```ruby
-  Minecraft::Data.head_url_of('069a79f4-44e9-4726-a5be-fca90e38aaf5', true)
-  Minecraft::Data.head_url_of('069a79f4-44e9-4726-a5be-fca90e38aaf5', false)
+  Minecraft::Data.head_url_of('069a79f4-44e9-4726-a5be-fca90e38aaf5', true, 90)
+  Minecraft::Data.head_url_of('069a79f4-44e9-4726-a5be-fca90e38aaf5', false, 180)
 ```
 
 Output:
 ```
-  https://crafatar.com/avatars/2cef6d05-ec9a-44b3-bedc-53359c68ae65?overlay
-  https://crafatar.com/avatars/2cef6d05-ec9a-44b3-bedc-53359c68ae65
+  https://crafatar.com/avatars/2cef6d05-ec9a-44b3-bedc-53359c68ae65?overlay&size=90
+  https://crafatar.com/avatars/2cef6d05-ec9a-44b3-bedc-53359c68ae65?size=180
 ```
 
 ## Development

data/lib/minecraft/data/version.rb

@@ -1,5 +1,5 @@
 module Minecraft
   module Data
-    VERSION = '0.1.1'.freeze
+    VERSION = '0.1.2'.freeze
   end
 end

data/lib/minecraft/data.rb

@@ -72,11 +72,11 @@ module Minecraft
         end
       end
 
-      def head_url_of(uuid, overlay)
+      def head_url_of(uuid, overlay, size)
         if overlay
-          "#{HEADS_API}/#{uuid}?overlay"
+          "#{HEADS_API}/#{uuid}?overlay&size=#{size}"
         else
-          "#{HEADS_API}/#{uuid}"
+          "#{HEADS_API}/#{uuid}&size=#{size}"
         end
       end
     end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: minecraft-data
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.1.2
 platform: ruby
 authors:
 - José Benavente
@@ -54,8 +54,6 @@ files:
 - ".github/CODEOWNERS"
 - ".gitignore"
 - ".rspec"
-- ".travis.yml"
-- CODE_OF_CONDUCT.md
 - Gemfile
 - Gemfile.lock
 - LICENCE.txt
@@ -65,7 +63,6 @@ files:
 - bin/setup
 - lib/minecraft/data.rb
 - lib/minecraft/data/version.rb
-- minecraft-data-0.1.0.gem
 - minecraft-data.gemspec
 homepage: https://github.com/BGMP/minecraft-data
 licenses:

data/.travis.yml

@@ -1,6 +0,0 @@
----
-language: ruby
-cache: bundler
-rvm:
-  - 2.6.5
-before_install: gem install bundler -v 2.1.4

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 bgmp00@protonmail.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 [https://contributor-covenant.org/version/1/4][version]
-
-[homepage]: https://contributor-covenant.org
-[version]: https://contributor-covenant.org/version/1/4/