webfleet_connect 0.1.0 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: cd7bb4f3c1e270c5d567ce1a3b7a876d2e77325dc0ceccdce798212ec0d02bac
-  data.tar.gz: 4aceeb6e7517ced274aab6c64ed481af1f61813de2f4b96903f748cfab9dcb48
+  metadata.gz: 3bbee91ece2cfe95d2f2b846649c0c54fafd21cfe5148740a21ad999af5102ba
+  data.tar.gz: f81b1ce8e66dea4ade1f658f701729dbc66f7e97114803ec4dbc3ae61278f590
 SHA512:
-  metadata.gz: daf1f0aca012f1a5a2c6389fc959739f6c8ee3edebbfb0c3c41ee516fb90c879b4b2861cbcf1c6a932fce352aaca51ee15cd088b8c3f227b0a0b1c19010ce302
-  data.tar.gz: b486fe3c27993c4c1d45ab11f261d0b248221afa03f81c12f2a60404ca49acf580e893297b806fcd70ecc471a1726376deaf7d3191245e5bfd1e5aa2d3b97b1c
+  metadata.gz: '011081d1736500a31b39fa430fcd6c9cb64d305718bcea662a053cea98877cfb790b01a3d98c3fa7858c3f173e5951591f59d6b42702c6d650a0d6e25433018c'
+  data.tar.gz: bd0d10a474ad221333ded8b5e5c8003b43d423af210ed10d3b30cae12d954b01b860defc1699cd8731532081477c972f77ec961ea0c4da6519e5013b4dd5fb15

data/README.md

@@ -6,6 +6,8 @@
 
 Gem to consume WEBFLEET.connect API.
 
+[![Gem Version](https://badge.fury.io/rb/webfleet_connect.svg)](https://badge.fury.io/rb/webfleet_connect)
+
 The WEBFLEET.connect API connects software appli­ca­tions with the Webfleet fleet management solution. Via WEBFLEET.connect you can enhance the value of all types of business solutions, including routing and scheduling optimization, ERP, Transport Management System (TMS), supply chain planning, asset management, and much more.
 
 ## Installation
@@ -36,7 +38,7 @@ response.to_hash # [{:objectno=>"858EU4", :objectname=>"YRT-MMD2439", :objectcla
 
 `WebfleetConnect.create` returns a new `WebfleetConnect::Session` object which has the capabilities to request info from the WEBFLEET.connect API.
 
-The Webfllet credential are taken from the env variables `WEBFLEET_CONNECT_ACCOUNT`, `WEBFLEET_CONNECT_USERNAME`, `WEBFLEET_CONNECT_PASSWORD` and `WEBFLEET_CONNECT_APIKEY` (if you want to know more about env variables check [this link](https://www.honeybadger.io/blog/ruby-guide-environment-variables/)).
+The Webfleet credential are taken from the env variables `WEBFLEET_CONNECT_ACCOUNT`, `WEBFLEET_CONNECT_USERNAME`, `WEBFLEET_CONNECT_PASSWORD` and `WEBFLEET_CONNECT_APIKEY` (if you want to know more about env variables check [this link](https://www.honeybadger.io/blog/ruby-guide-environment-variables/)).
 
 If your system needs to work with multiple accounts or you need to specify the credentials dynamically for some other reason, you can do it this way:
 

data/lib/webfleet_connect/session.rb

@@ -10,7 +10,7 @@ require_relative 'actions/trips'
 require_relative 'connection'
 
 module WebfleetConnect
-  class WebfleetConnect::Session
+  class Session
     include Actions::Addresses
     include Actions::Drivers
     include Actions::Events

data/lib/webfleet_connect/version.rb

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

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: webfleet_connect
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors:
 - alex
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2023-08-23 00:00:00.000000000 Z
+date: 2023-08-24 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: httparty
@@ -131,6 +131,7 @@ files:
 - lib/webfleet_connect/response.rb
 - lib/webfleet_connect/session.rb
 - lib/webfleet_connect/version.rb
+- pkg/.gitkeep
 - sig/webfleet_connect.rbs
 - webfleet_connect.gemspec
 homepage: https://movomx.com