You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*[#174](https://github.com/bigcommerce/bigcommerce-api-ruby/pull/174): Drop support for ruby 2.6; Add support for Ruby 3.2 - [@j05h](https://github.com/j05h).
Go to https://github.com/contributor/bigcommerce-api-ruby and select your feature branch. Click the 'Pull Request' button and fill out the form. Pull requests are usually reviewed within a few days.
88
+
Go to https://github.com/contributor/bigcommerce-api-ruby and select your feature branch. Click the 'Pull Request'
89
+
button and fill out the form. Pull requests are usually reviewed within a few days.
Go back to your pull request after a few minutes and see whether it passed muster with Travis-CI. Everything should look green, otherwise fix issues and amend your commit as described above.
118
+
Go back to your pull request after a few minutes and see whether it passed muster with CircleCI. Everything should
119
+
look green, otherwise fix issues and amend your commit as described above.
This is the official BigCommerce API client to support our Stores API. You can find more information about becoming a BigCommerce developer here: [developer.bigcommerce.com](http://developer.bigcommerce.com).
8
+
This is the official BigCommerce API client to support our Stores API. You can find more information about becoming a
To make requests to our API, you must register as a developer and have your credentials ready.
30
31
31
-
Also very important: For the OAuth authentication mechanism, the resources to which you have acccess depend on the scopes that the merchant has granted to your application. For more information about Store API scopes, see: [OAuth Scopes](https://developer.bigcommerce.com/api/scopes).
32
+
Also very important: For the OAuth authentication mechanism, the resources to which you have acccess depend on the
33
+
scopes that the merchant has granted to your application. For more information about Store API scopes,
We currently have two different authentication schemes that you can select, depending on your use case.
35
38
36
39
### OAuth
37
-
OAuth apps can be submitted to [BigCommerce App Store](https://www.bigcommerce.com/apps), allowing other merchants to install these apps in their BigCommerce stores.
40
+
OAuth apps can be submitted to [BigCommerce App Store](https://www.bigcommerce.com/apps), allowing other merchants to install these apps in their
To get all the basic auth credentials, simply visit your store admin page, and navigate to the `Advanced Settings` > `Legacy API Settings`. Once there, you can create a new legacy API account on which to authenticate.
69
+
To get all the basic auth credentials, simply visit your store admin page, and navigate to the
70
+
`Advanced Settings` > `Legacy API Settings`. Once there, you can create a new legacy API account on which to authenticate.
71
+
66
72
67
73
```rb
68
74
Bigcommerce.configure do |config|
@@ -75,7 +81,8 @@ end
75
81
76
82
__SSL Configuration__
77
83
78
-
If you are using your own, self-signed, certificate, you can pass SSL options to Faraday. This is not required, but might be useful in special edge cases.
84
+
If you are using your own, self-signed, certificate, you can pass SSL options to Faraday. This is not required, but
85
+
might be useful in special edge cases.
79
86
80
87
```rb
81
88
Bigcommerce.configure do |config|
@@ -95,7 +102,8 @@ For more information about configuring SSL with Faraday, please see the followin
95
102
-[Faraday: Setting up SSL certificates](https://github.com/lostisland/faraday/wiki/Setting-up-SSL-certificates)
96
103
97
104
### Customer Login API
98
-
If you want to generate tokens for storefront login using the Customer Login API, you need to configure your app's client secret.
105
+
If you want to generate tokens for storefront login using the Customer Login API, you need to configure your app's
106
+
client secret.
99
107
100
108
-```store_hash```: The store hash of the store you are operating against.
101
109
-```client_id```: Obtained from the on the BigCommerce [Developer Portal's](http://developer.bigcommerce.com) "My Apps" section.
@@ -110,7 +118,8 @@ end
110
118
```
111
119
112
120
## Usage
113
-
For full examples of using the API client, please see the [examples folder](examples) and refer to BigCommerce's [developer documentation](https://developer.bigcommerce.com/api).
121
+
For full examples of using the API client, please see the [examples folder](examples) and refer to
The `Bigcommerce.configure` method is NOT thread-safe. This mechanism is designed for applications or CLI's (command-line interfaces) where thread safety is not a concern. If you need to guarantee thread safety, we support this alternative mechanism to make thread-safe API requests:
141
+
The `Bigcommerce.configure` method is NOT thread-safe. This mechanism is designed for applications or
142
+
CLIs (command-line interfaces) where thread safety is not a concern. If you need to guarantee thread safety, we support
143
+
this alternative mechanism to make thread-safe API requests:
133
144
134
-
Rather then setting up a single `connection` for all API requests, you would construct a new connection for each thread. If you can ensure that each of these connections is stored in a thread-safe manner, you can pass the `connection` as you query the resource.
145
+
Rather then setting up a single `connection` for all API requests, construct a new connection for each thread.
146
+
If you can ensure that each of these connections is stored in a thread-safe manner, you can pass the `connection` as
147
+
you query the resource.
135
148
136
-
This connection is nothing more than a `Faraday::Connection` – so if you want to write your own, or to use your own adapters, you can feel free. Please refer to this gem's [connection class](https://github.com/bigcommerce/bigcommerce-api-ruby/blob/master/lib/bigcommerce/connection.rb) for more details.
149
+
This connection is nothing more than a `Faraday::Connection` – so if you want to write your own, or to use your own
150
+
adapters, you can feel free. Please refer to this gem's [connection class](https://github.com/bigcommerce/bigcommerce-api-ruby/blob/master/lib/bigcommerce/connection.rb) for more details.
Copy file name to clipboardExpand all lines: RELEASING.md
+4-2
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,7 @@
1
1
# Releasing Bigcommerce API Client
2
2
3
-
There're no particular rules about when to release the Bigcommerce API client. Release bug fixes frequently, features not so frequently, and breaking API changes rarely.
3
+
There are no particular rules about when to release the Bigcommerce API client. Release bug fixes frequently, features
4
+
not so frequently, and breaking API changes rarely.
4
5
5
6
### Before A Release
6
7
@@ -11,7 +12,8 @@ bundle install
11
12
bundle exec rake
12
13
```
13
14
14
-
This will ensure both style and that all the specs pass locally. Next, check that the last build succeeded in [CircleCI](https://app.circleci.com/pipelines/github/bigcommerce/bigcommerce-api-ruby) for all supported platforms.
15
+
This will ensure both style and that all the specs pass locally. Next, check that the last build succeeded
16
+
in [CircleCI](https://app.circleci.com/pipelines/github/bigcommerce/bigcommerce-api-ruby) for all supported platforms.
15
17
16
18
Increment the version, modify [lib/bigcommerce/version.rb](lib/bigcommerce/version.rb).
0 commit comments