coinmarketcal 0.1.1 → 0.1.2

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    MWViMjJmZWNhMTlhZmVlZWViZjU0NTAyZGI1OGMyNjM4ZTVkMWQyOQ==
+    NzdjNjAxMjc4MjUxYjA2YTBiZDdiODM2ZDA3OTBiMjA4ZjRjMDM2Nw==
   data.tar.gz: !binary |-
-    NWRkNTI2ZTIwNTIwNmIwMTdhYTY5MDc2NWY5NjMzMDUyMTVmOTRiYQ==
+    ZTlmZTNjYjkxYzkyYWIxNDQ0NzQxNjhjM2UzZTBkZWY3OTE2MDRiNA==
 SHA512:
   metadata.gz: !binary |-
-    NmRiYzNmM2FkOWM4YzYwMWUxZGU0MjJkZWQwNzU0MzFlNzgyMzc1NjZhZWJk
-    NDg5OTE2Y2I5ODhjNzg2ODc3MTc4NTI1MjUzY2M2ZWFhNzBkZmMyNWUzMTQx
-    NjFkYzE1YjIzYWQwNjMyYjg5NmI0MmIwODQyYTZkYjY2YWY5ZDI=
+    NjUyMTk1OGIyNmMzOTA4MmM0MTdiYWYwYWU4OWYzNjMyZGE5ZGRmNTFkM2Uw
+    NDMwM2QxNjY3NWZmMmMzZmE4YTNiOTE5Y2RjYThhYmFjNDk3MmE2MTNmMmM2
+    Y2MyNzY3OGE0YzdiZjVhNWQ4NjYxODNlNDdlODIxNmExN2I0MTU=
   data.tar.gz: !binary |-
-    NTk5OWEzZjJmNGRlYmZmMGFhM2JkYjIyOGUyN2FjZTgwNjczNTljNmVkODIy
-    ZTMzMzY1YzBkZWY1YTE5ZGE0NmI5Zjk3MDNmN2FmMmQ1ZDI0YjE2YzBhMGZl
-    YTRkZGNkOGNjM2Y3MGFmMjg3ZDI2ZDEzOWFjOWM5OTlhYTNhYWQ=
+    ZmRkNGZmNDY5MWU2YjFlYmI2MTI0ZjdjNWE2ZGE5ZjdhNGE5NDRjZWVkNjRl
+    MzQ4OThiODg0NGZhMWI0OTc1YzUyZjA5ZjEzYjI2MDBlZWY1ZTExNjVmMjQx
+    ZGVlNDBiZWUyMjNmMTlkYTRhMThiYjAzN2IxNTYzZjg3MGUyYTA=

data/.gitignore

@@ -9,3 +9,12 @@
 
 # rspec failure tracking
 .rspec_status
+
+# Gem builds
+pkg
+
+# Don't include your lock file
+Gemfile.lock
+
+# Don't include Rubymine config
+.idea

data/README.md

@@ -1,8 +1,8 @@
-# Coinmarketcal
+# Coinmarketcal [![Gem Version](https://badge.fury.io/rb/coinmarketcal.svg)](https://badge.fury.io/rb/coinmarketcal)
 
-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/coinmarketcal`. To experiment with that code, run `bin/console` for an interactive prompt.
+Unofficial gem for the CoinMarketCal API.
 
-TODO: Delete this and the text above, and describe your gem
+CoinMarketCal is the economic calendar for the cryptocurrency market. Evidence-based and community-driven.
 
 ## Installation
 
@@ -22,22 +22,41 @@ Or install it yourself as:
 
 ## Usage
 
-TODO: Write usage instructions here
+You can authenticate access to your CoinMarketCal account by configuring your implementation of the coinmarketcal gem. This is accomplished by using a config block at the top of your application.
 
-## Development
+Set up your keys at: https://api.coinmarketcal.com/developer/dashboard
 
-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.
+```ruby
+Coinmarketcal.config do |c|
+  c.client_id = 'your-client-id'
+  c.client_secret = 'your-client-secret'
+end
+```
+
+To retrieve list of coins:
+```ruby
+Coinmarketcal::Coin.all
+```
+
+To retrieve list of events:
+```ruby
+Coinmarketcal::Event.all
+```
+
+To retrieve list of categories:
+```ruby
+Coinmarketcal::Category.all
+```
 
-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/[USERNAME]/coinmarketcal. 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.
+1. Fork it ( https://github.com/toreserter/coinmarketcal/fork )
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Add some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create a new Pull Request
 
 ## 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 Coinmarketcal project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/coinmarketcal/blob/master/CODE_OF_CONDUCT.md).

data/lib/coinmarketcal/event.rb

@@ -12,15 +12,15 @@ module Coinmarketcal
 
     def self.all(attrs = {})
       search_hash = {
-          page: (attrs['page'] || 1),
-          max: attrs['max'],
-          dateRangeStart: attrs['date_range_start'],
-          dateRangeEnd: attrs['date_range_end'],
-          coins: attrs['coins'],
-          categories: attrs['categories'],
-          sortBy: attrs['sort_by'],
-          showOnly: attrs['show_only'],
-          showMetadata: attrs['show_metadata']
+          page: (attrs[:page] || 1),
+          max: attrs[:max],
+          dateRangeStart: attrs[:date_range_start],
+          dateRangeEnd: attrs[:date_range_end],
+          coins: attrs[:coins],
+          categories: attrs[:categories],
+          sortBy: attrs[:sort_by],
+          showOnly: attrs[:show_only],
+          showMetadata: attrs[:show_metadata]
       }
       client.get('v1/events', compact(search_hash)).map { |data| new(data) }
     end

data/lib/coinmarketcal/version.rb

@@ -1,3 +1,3 @@
 module Coinmarketcal
-  VERSION = "0.1.1"
+  VERSION = "0.1.2"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: coinmarketcal
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.1.2
 platform: ruby
 authors:
 - Tore Serter
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2018-07-03 00:00:00.000000000 Z
+date: 2018-07-04 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -76,9 +76,7 @@ files:
 - .gitignore
 - .rspec
 - .travis.yml
-- CODE_OF_CONDUCT.md
 - Gemfile
-- Gemfile.lock
 - LICENSE.txt
 - README.md
 - Rakefile
@@ -112,7 +110,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.6.8
+rubygems_version: 2.6.14
 signing_key: 
 specification_version: 4
 summary: Unofficial API Client for the CoinMarketCal API

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 toreserter@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.lock

@@ -1,27 +0,0 @@
-PATH
-  remote: .
-  specs:
-    coinmarketcal (0.1.0)
-      faraday (~> 0.12)
-      faraday_middleware (~> 0.12)
-
-GEM
-  remote: https://rubygems.org/
-  specs:
-    faraday (0.15.2)
-      multipart-post (>= 1.2, < 3)
-    faraday_middleware (0.12.2)
-      faraday (>= 0.7.4, < 1.0)
-    multipart-post (1.2.0)
-    rake (10.0.4)
-
-PLATFORMS
-  ruby
-
-DEPENDENCIES
-  bundler (~> 1.16)
-  coinmarketcal!
-  rake (~> 10.0)
-
-BUNDLED WITH
-   1.16.1