shopify_api 13.1.0 → 13.2.0

data/.github/workflows/stale.yml

@@ -1,43 +0,0 @@
-name: Close inactive issues / prs
-on:
-  schedule:
-    - cron: "30 1 * * *"
-
-jobs:
-  stale:
-    runs-on: ubuntu-latest
-    permissions:
-      issues: write
-      pull-requests: write
-    steps:
-      - uses: actions/stale@v7
-        with:
-          days-before-issue-stale: 60
-          days-before-issue-close: 14
-          days-before-pr-stale: 60
-          days-before-pr-close: 14
-          operations-per-run: 1000
-          stale-issue-label: "Stale"
-          stale-pr-label: "Stale"
-          stale-issue-message: >
-            This issue is stale because it has been open for 60 days with no activity. It will be closed if no further action occurs in 14 days.
-          close-issue-message: |
-            We are closing this issue because it has been inactive for a few months.
-            This probably means that it is not reproducible or it has been fixed in a newer version.
-            If it’s an enhancement and hasn’t been taken on since it was submitted, then it seems other issues have taken priority.
-
-            If you still encounter this issue with the latest stable version, please reopen using the issue template. You can also contribute directly by submitting a pull request– see the [CONTRIBUTING.md](https://github.com/Shopify/shopify-api-ruby/blob/main/CONTRIBUTING.md) file for guidelines
-
-            Thank you!
-          stale-pr-message: >
-            This pull request is stale because it has been open for 60 days with no activity. It will be closed if no further action occurs in 14 days.
-          close-pr-message: |
-            We are closing this pull request because it has been inactive for a few months.
-            This probably means that it is not reproducible or it has been fixed in a newer version.
-            If it’s an enhancement and hasn’t been taken on since it was submitted, then it seems other issues have taken priority.
-
-            If you still encounter this pull request with the latest stable version, please reopen using the pull request template. You can also contribute directly by submitting a pull request– see the [CONTRIBUTING.md](https://github.com/Shopify/shopify-api-ruby/blob/main/CONTRIBUTING.md) file for guidelines
-
-            Thank you!
-          repo-token: ${{ github.token }}
-          close-issue-reason: "not_planned"

data/docs/issues.md

@@ -1,39 +0,0 @@
-# Known issues and caveats
-
-By following this guide, you will have a fully functional Shopify app. However, there are some things you should be aware of before using your new app in a production environment.
-
-## Notes on session handling
-
-Before you start writing your application, please note that the Shopify library needs to store some information for OAuth in sessions. Since each application may choose a different strategy to store information, the library cannot dictate any specific storage strategy. When calling `ShopifyAPI::Context.setup`, you'll need to provide an instance of a class that implements the `ShopifyAPI::Auth::SessionStorage` interface.
-
-This library provides a very simple implementation of that interface which stores sessions in files, `ShopifyAPI::Auth::FileSessionStorage` ([source code](../lib/shopify_api/auth/file_session_storage.rb)). This class is meant to speed up development with this library, but it is not suitable for production use, because it will lead to disk build-up as old sessions are not cleaned up.
-
-Before you deploy your app to production, it should use your selected storage method for sessions. You can do that by creating a class that implements the `SessionStorage` interface and pass that in your `Context.setup` call. Your class will need to implement the methods below.
-
-**Note**: After you create your implementation of `SessionStorage`, you should make sure to clean up old sessions periodically in your data storage. The library will delete some sessions when they are no longer useful, but it cannot guarantee that expired sessions are deleted automatically.
-
-#### `SessionStorage.storeSession`
-
-Creates **or updates** a `Session` object in your storage. This function should return a `bool` indicating whether the operation was successful.
-
-| Param     | Type      | Notes                       |
-| --------- | --------- | --------------------------- |
-| `session` | `Session` | The session object to store |
-
-#### `SessionStorage.loadSession`
-
-Fetches a `Session` object from your storage. This function should return a `Session` object, or `null` if it was not found.
-
-| Param       | Type     | Notes                         |
-| ----------- | -------- | ----------------------------- |
-| `sessionId` | `string` | The id of the session to load |
-
-#### `SessionStorage.deleteSession`
-
-Deletes a session from your storage. This function should return a `bool` indicating whether the operation was successful.
-
-| Param       | Type     | Notes                           |
-| ----------- | -------- | ------------------------------- |
-| `sessionId` | `string` | The id of the session to delete |
-
-[Back to guide index](README.md)

data/docs/usage/session_storage.md

@@ -1,46 +0,0 @@
-
-# Create a Session Storage Implementation
-
-The implementation of session storage that you pass in `ShopifyAPI::Context.setup` is what the Shopify gem will use to store and load sessions. [Shopify::Auth::FileSessionStorage](../../lib/shopify_api/auth/file_session_storage.rb) can be used for testing purposes and as an example of how to make an implementation in your app. This is not recommended for production, we recommend you implement a solution that will store and load serialized sessions from a more ideal store such as a database like MySQL or MongoDB.
-
-## Create a New Session Storage Class
-
-You can create a session storage class that includes `ShopifyAPI::Auth::SessionStorage` and override the methods as shown in the table and example below:
-
-|       Method Name      |             Input Type            |           Return Type          |
-| ---------------------- | --------------------------------- | ------------------------------ |
-| `store_session`        | `ShopifyAPI::Auth::Session`       | `Boolean` (true if successful) |
-| `load_session`         | `String` (session id)             | `ShopifyAPI::Auth::Session`    |
-| `delete_session`       | `String` (session id)             | `Boolean` (true if successful) |
-
-
-```ruby
-class CustomSessionStorage
-  include ShopifyAPI::Auth::SessionStorage
-
-  def initialize
-    # Initialize as needed
-  end
-
-  def store_session(session)
-    # Implement a store function
-    some_store_function(id: session.id, session_data: session.serialize)
-  end
-
-  def load_session(id)
-    # Implement a fetch function
-    session_data = some_fetch_function(id)
-    ShopifyAPI::Auth::Session.deserialize(session_data)
-  end
-
-  def delete_session(id)
-    # Implement a delete function
-    some_delete_function(id)
-    true
-  end
-end
-```
-
-**Note:** We recommend utilizing the Session `serialize` and `deserialize` functions to make storing and loading sessions easier.
-
-Once this is complete you can pass an instance of this session storage class as `session_storage` in `ShopifyAPI::Context.setup`