get_around_owner 1.0.0 → 1.0.1

data/docs/UnavailabilitiesApi.md

@@ -1,135 +0,0 @@
-# GetAroundOwner::UnavailabilitiesApi
-
-All URIs are relative to *https://api-eu.getaround.com/owner/v1*
-
-| Method | HTTP request | Description |
-| ------ | ------------ | ----------- |
-| [**created_unavailability_post**](UnavailabilitiesApi.md#created_unavailability_post) | **POST** /createdUnavailability | Unavailability created on one of your cars |
-| [**deleted_unavailability_post**](UnavailabilitiesApi.md#deleted_unavailability_post) | **POST** /deletedUnavailability | Unavailabilities deleted on one of your cars |
-
-
-## created_unavailability_post
-
-> created_unavailability_post(opts)
-
-Unavailability created on one of your cars
-
-### Examples
-
-```ruby
-require 'time'
-require 'get_around_owner'
-
-api_instance = GetAroundOwner::UnavailabilitiesApi.new
-opts = {
-  getaround_unavailabilities_created:  # GetaroundUnavailabilitiesCreated | This event is triggered whenever an unavailability is created (through the API or directly in the app/website). It shows the unavailability that has just been created, with the same timestamps as those entered by the user. It does not show the changes of other potential overlapping unavailabilities. For example: if an unavailability was already set between June 10 and June 20, and if the user creates a new one between June 18 and June 22, this webhook will only send information about the newly created June 18 - June 22 unavailability. It will not show that, under the hood, the unavailability from June 10 to June 20 has be deleted, and that a new unavailability from June 10 to June 22 has been created.
-}
-
-begin
-  # Unavailability created on one of your cars
-  api_instance.created_unavailability_post(opts)
-rescue GetAroundOwner::ApiError => e
-  puts "Error when calling UnavailabilitiesApi->created_unavailability_post: #{e}"
-end
-```
-
-#### Using the created_unavailability_post_with_http_info variant
-
-This returns an Array which contains the response data (`nil` in this case), status code and headers.
-
-> <Array(nil, Integer, Hash)> created_unavailability_post_with_http_info(opts)
-
-```ruby
-begin
-  # Unavailability created on one of your cars
-  data, status_code, headers = api_instance.created_unavailability_post_with_http_info(opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => nil
-rescue GetAroundOwner::ApiError => e
-  puts "Error when calling UnavailabilitiesApi->created_unavailability_post_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **getaround_unavailabilities_created** | [**GetaroundUnavailabilitiesCreated**](GetaroundUnavailabilitiesCreated.md) | This event is triggered whenever an unavailability is created (through the API or directly in the app/website). It shows the unavailability that has just been created, with the same timestamps as those entered by the user. It does not show the changes of other potential overlapping unavailabilities. For example: if an unavailability was already set between June 10 and June 20, and if the user creates a new one between June 18 and June 22, this webhook will only send information about the newly created June 18 - June 22 unavailability. It will not show that, under the hood, the unavailability from June 10 to June 20 has be deleted, and that a new unavailability from June 10 to June 22 has been created. | [optional] |
-
-### Return type
-
-nil (empty response body)
-
-### Authorization
-
-No authorization required
-
-### HTTP request headers
-
-- **Content-Type**: application/json
-- **Accept**: Not defined
-
-
-## deleted_unavailability_post
-
-> deleted_unavailability_post(opts)
-
-Unavailabilities deleted on one of your cars
-
-### Examples
-
-```ruby
-require 'time'
-require 'get_around_owner'
-
-api_instance = GetAroundOwner::UnavailabilitiesApi.new
-opts = {
-  getaround_unavailabilities_deleted:  # GetaroundUnavailabilitiesDeleted | This event is triggered whenever an unavailability is deleted (through the API or directly in the app/website). It shows the unavailability that has just been deleted, with the same timestamps as those entered by the user. It does not show the changes of other potential overlapping unavailabilities. For example: if an unavailability was already set between June 10 and June 20, and if the user deletes an unavailability between June 18 and June 22 (to set their car as available between this dates), this webhook will only send information about the newly deleted June 18 - June 22 unavailability. It will not show that, under the hood, the unavailability from June 10 to June 20 has be deleted, and that a new unavailability from June 10 to June 18 has been created.
-}
-
-begin
-  # Unavailabilities deleted on one of your cars
-  api_instance.deleted_unavailability_post(opts)
-rescue GetAroundOwner::ApiError => e
-  puts "Error when calling UnavailabilitiesApi->deleted_unavailability_post: #{e}"
-end
-```
-
-#### Using the deleted_unavailability_post_with_http_info variant
-
-This returns an Array which contains the response data (`nil` in this case), status code and headers.
-
-> <Array(nil, Integer, Hash)> deleted_unavailability_post_with_http_info(opts)
-
-```ruby
-begin
-  # Unavailabilities deleted on one of your cars
-  data, status_code, headers = api_instance.deleted_unavailability_post_with_http_info(opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => nil
-rescue GetAroundOwner::ApiError => e
-  puts "Error when calling UnavailabilitiesApi->deleted_unavailability_post_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **getaround_unavailabilities_deleted** | [**GetaroundUnavailabilitiesDeleted**](GetaroundUnavailabilitiesDeleted.md) | This event is triggered whenever an unavailability is deleted (through the API or directly in the app/website). It shows the unavailability that has just been deleted, with the same timestamps as those entered by the user. It does not show the changes of other potential overlapping unavailabilities. For example: if an unavailability was already set between June 10 and June 20, and if the user deletes an unavailability between June 18 and June 22 (to set their car as available between this dates), this webhook will only send information about the newly deleted June 18 - June 22 unavailability. It will not show that, under the hood, the unavailability from June 10 to June 20 has be deleted, and that a new unavailability from June 10 to June 18 has been created. | [optional] |
-
-### Return type
-
-nil (empty response body)
-
-### Authorization
-
-No authorization required
-
-### HTTP request headers
-
-- **Content-Type**: application/json
-- **Accept**: Not defined
-

data/docs/UsersApi.md

@@ -1,71 +0,0 @@
-# GetAroundOwner::UsersApi
-
-All URIs are relative to *https://api-eu.getaround.com/owner/v1*
-
-| Method | HTTP request | Description |
-| ------ | ------------ | ----------- |
-| [**updated_user_post**](UsersApi.md#updated_user_post) | **POST** /updatedUser | User updated his profile information |
-
-
-## updated_user_post
-
-> updated_user_post(opts)
-
-User updated his profile information
-
-### Examples
-
-```ruby
-require 'time'
-require 'get_around_owner'
-
-api_instance = GetAroundOwner::UsersApi.new
-opts = {
-  getaround_users_updated:  # GetaroundUsersUpdated | This event is triggered when a user updates his profile information (You will only receive this event on users with a booked rental or a started rental).
-}
-
-begin
-  # User updated his profile information
-  api_instance.updated_user_post(opts)
-rescue GetAroundOwner::ApiError => e
-  puts "Error when calling UsersApi->updated_user_post: #{e}"
-end
-```
-
-#### Using the updated_user_post_with_http_info variant
-
-This returns an Array which contains the response data (`nil` in this case), status code and headers.
-
-> <Array(nil, Integer, Hash)> updated_user_post_with_http_info(opts)
-
-```ruby
-begin
-  # User updated his profile information
-  data, status_code, headers = api_instance.updated_user_post_with_http_info(opts)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => nil
-rescue GetAroundOwner::ApiError => e
-  puts "Error when calling UsersApi->updated_user_post_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **getaround_users_updated** | [**GetaroundUsersUpdated**](GetaroundUsersUpdated.md) | This event is triggered when a user updates his profile information (You will only receive this event on users with a booked rental or a started rental). | [optional] |
-
-### Return type
-
-nil (empty response body)
-
-### Authorization
-
-No authorization required
-
-### HTTP request headers
-
-- **Content-Type**: application/json
-- **Accept**: Not defined
-

data/get_around_owner.gemspec

@@ -1,26 +0,0 @@
-# -*- encoding: utf-8 -*-
-
-$:.push File.expand_path("../lib", __FILE__)
-require "get_around_owner/version"
-
-Gem::Specification.new do |s|
-  s.name        = "get_around_owner"
-  s.version     = GetAroundOwner::VERSION
-  s.platform    = Gem::Platform::RUBY
-  s.authors     = ["OpenAPI-Generator", "yann120"]
-  s.homepage    = "https://openapi-generator.tech"
-  s.summary     = "Getaround Owner API Ruby Gem"
-  s.description = "Getaround Owner API Wrapper"
-  s.license     = "Unlicense"
-  s.required_ruby_version = ">= 2.7"
-  s.metadata    = {}
-
-  s.add_runtime_dependency 'typhoeus', '~> 1.0', '>= 1.0.1'
-
-  s.add_development_dependency 'rspec', '~> 3.6', '>= 3.6.0'
-
-  s.files         = `find *`.split("\n").uniq.sort.select { |f| !f.empty? }
-  s.test_files    = `find spec/*`.split("\n")
-  s.executables   = []
-  s.require_paths = ["lib"]
-end

data/git_push.sh

@@ -1,57 +0,0 @@
-#!/bin/sh
-# ref: https://help.github.com/articles/adding-an-existing-project-to-github-using-the-command-line/
-#
-# Usage example: /bin/sh ./git_push.sh wing328 openapi-petstore-perl "minor update" "gitlab.com"
-
-git_user_id=$1
-git_repo_id=$2
-release_note=$3
-git_host=$4
-
-if [ "$git_host" = "" ]; then
-    git_host="github.com"
-    echo "[INFO] No command line input provided. Set \$git_host to $git_host"
-fi
-
-if [ "$git_user_id" = "" ]; then
-    git_user_id="GIT_USER_ID"
-    echo "[INFO] No command line input provided. Set \$git_user_id to $git_user_id"
-fi
-
-if [ "$git_repo_id" = "" ]; then
-    git_repo_id="GIT_REPO_ID"
-    echo "[INFO] No command line input provided. Set \$git_repo_id to $git_repo_id"
-fi
-
-if [ "$release_note" = "" ]; then
-    release_note="Minor update"
-    echo "[INFO] No command line input provided. Set \$release_note to $release_note"
-fi
-
-# Initialize the local directory as a Git repository
-git init
-
-# Adds the files in the local repository and stages them for commit.
-git add .
-
-# Commits the tracked changes and prepares them to be pushed to a remote repository.
-git commit -m "$release_note"
-
-# Sets the new remote
-git_remote=$(git remote)
-if [ "$git_remote" = "" ]; then # git remote not defined
-
-    if [ "$GIT_TOKEN" = "" ]; then
-        echo "[INFO] \$GIT_TOKEN (environment variable) is not set. Using the git credential in your environment."
-        git remote add origin https://${git_host}/${git_user_id}/${git_repo_id}.git
-    else
-        git remote add origin https://${git_user_id}:"${GIT_TOKEN}"@${git_host}/${git_user_id}/${git_repo_id}.git
-    fi
-
-fi
-
-git pull origin master
-
-# Pushes (Forces) the changes in the local repository up to the remote repository
-echo "Git pushing to https://${git_host}/${git_user_id}/${git_repo_id}.git"
-git push origin master 2>&1 | grep -v 'To https'