bullet_train 1.2.5 → 1.2.7

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: fa2dfac5d71da28521ac903aef4acba2c5834f2da5c83ed89f4eb2dd1badf143
-  data.tar.gz: 7786d24e4271cf0547b495addefabbc46b0aaf58eb1672a3ab24ff5cb22a366e
+  metadata.gz: a8af0861111947e0fad526fe89c7d1b6180f65b9122610eeaf26f8503ba50fed
+  data.tar.gz: 307372ed882d3e0e07f4a32810926cbeaf9497561d4db4faa1927765657ec961
 SHA512:
-  metadata.gz: cf4cb1f74f1c85df573e544a7e6d03eac8d0db92a7fdb847de163d26527d153d7343cef139450e88d4d5332fe3728fbc9dc61f592ad84eeaf314bc40f378b40c
-  data.tar.gz: a347aa6b5e8234d6a90ce95a3c3e19e372597b45d4272e1e9a6feecc28bfbbfe5d9e24e6bc914ceb7e95eb8cdf9b187bc7a564ee30d8bd6c5f9d5e089ea62782
+  metadata.gz: 993b1e6a8b6e73bad6f04c4e3c2caa1c3d5476ee0bea64972ee7ed9b2bfcefa69ebffc4af3fb3a33fdbbbd1fc8c49d0bd23c5f50894f2a7544132d3b6304ec5b
+  data.tar.gz: d76a30a93bab13b98f8e0ac8dbedab25c6eb74f7158211e200e74e4e636ede62eae4fa0be688601c3bf817a2ad73e218dad96a05db2cb77ef9b942fc95d6113a

data/app/controllers/concerns/documentation_support.rb

@@ -3,8 +3,14 @@ module DocumentationSupport
 
   def docs
     target = params[:page].presence || "index"
-    all_paths = ([Rails.root.to_s] + `bundle show --paths`.lines.map(&:chomp))
-    @path = all_paths.map { |path| path + "/docs/#{target}.md" }.detect { |path| File.exist?(path) }
+
+    # TODO For some reason this didn't work on Heroku.
+    # all_paths = ([Rails.root.to_s] + `bundle show --paths`.lines.map(&:chomp))
+    # @path = all_paths.map { |path| path + "/docs/#{target}.md" }.detect { |path| File.exist?(path) }
+
+    # TODO Trying to just brute force this for now.
+    @path = `bundle show bullet_train`.chomp + "/docs/#{target}.md"
+
     render :docs, layout: "docs"
   end
 end

data/app/views/layouts/docs.html.erb

@@ -215,15 +215,21 @@
               <% end %>
 
               <%= render 'account/shared/menu/section', title: 'Integration' do %>
-                <%= render 'account/shared/menu/item', url: '/docs/oauth', label: 'OAuth Providers' do |p| %>
+                <%= render 'account/shared/menu/item', url: '/docs/api', label: 'REST API' do |p| %>
                   <% p.content_for :icon do %>
-                    <i class="fal fa-at ti ti-reload"></i>
+                    <i class="fal fa-brackets-curly ti ti-settings"></i>
                   <% end %>
                 <% end %>
 
-                <%= render 'account/shared/menu/item', url: '/docs/api', label: 'REST API' do |p| %>
+                <%= render 'account/shared/menu/item', url: '/docs/zapier', label: 'Zapier' do |p| %>
                   <% p.content_for :icon do %>
-                    <i class="fal fa-brackets-curly ti ti-settings"></i>
+                    <i class="fal fa-bolt ti ti-bolt"></i>
+                  <% end %>
+                <% end %>
+
+                <%= render 'account/shared/menu/item', url: '/docs/oauth', label: 'OAuth Providers' do |p| %>
+                  <% p.content_for :icon do %>
+                    <i class="fal fa-at ti ti-reload"></i>
                   <% end %>
                 <% end %>
 

data/docs/api/versioning.md

@@ -0,0 +1,63 @@
+# API Versioning
+Bullet Train's API layer is designed to help support the need of software developers to evolve their API over time while continuing to maintain support for versions of the API that users have already built against.
+
+## What is API versioning?
+By default, Bullet Train will build out a "V1" version of your API. The version number is intended to represent a contract with your users that as long as they're hitting `/api/v1` endpoints, the structure of URLs, requests, and responses won't change in a way that will break the integrations they've created.
+
+If a change to the API would break the established contract, we want to bump the API version number so we can differentiate between developers building against the latest version of the API (e.g. "V2") and developers who wrote code against the earlier version of the API (e.g. "V1"). This allows us the opportunity to ensure that older versions of the API continue to work as previously expected by the earlier developers.
+
+## When should you take advantage of API versioning?
+You want to bump API versions as sparingly as possible. Even with all the tooling Bullet Train provides, maintaining backwards compatibility of older API versions comes at an ongoing cost. Generally speaking, you should only bump your API version when a customer is already using an API endpoint and you're making changes to the structure of your domain model that are not strictly additive and will break the established contract.
+
+Importantly, if the changes you're making to your domain model are only additive, you don't need to bump your API version. Users shouldn't care that you're adding new attributes or new endpoints to your API, just as long as the ones they're already using don't change in a way that is breaking for them.
+
+## Background
+By default, the following components in your API are created in versioned namespaces:
+
+ - API controllers are in `app/controllers/api/v1` and live in an `Api::V1` module.
+ - JSON views are in `app/controllers/api/v1`.
+ - Routes are in `config/routes/api/v1.rb`.
+ - Tests are in `test/controllers/api/v1` and live in an `Api::V1` module.
+
+> It's also impotant to keep in mind that some dependencies of your API and API tests like models, factories, and permissions are not versioned, but as we'll cover later, this is something our approach helps you work around.
+
+## Bumping Your API Version
+
+⚠️ You must do this _before_ making the breaking changes to your API.
+
+If you're in a situation where you know you need to bump your API version to help lock-in a backward compatible version of your API, you can simply run:
+
+```
+rake bullet_train:api:bump_version
+```
+
+> TODO This Rake task doesn't exist yet.
+
+## What happens when you bump an API version?
+When you bump your API version, all of the files and directories that are namespaced with the API version number will be duplicated into a new namespace for the new API version number.
+
+For example, when bumping from "V1" to "V2":
+
+ - A copy of all the API controllers in `app/controllers/api/v1` are copied into `app/controllers/api/v2`.
+ - A copy of all the JSON views in `app/views/api/v1` are copied into `app/views/api/v2`.
+ - A copy of all the routes in `config/routes/api/v1.rb` are copied into `config/routes/api/v2.rb`.
+ - A copy of all the tests in `test/controllers/api/v1` are copied into `test/controllers/api/v2`.
+
+We also bump the value of `BulletTrain::Api.current_version` in `config/initializers/api.rb` so tools like Super Scaffolding know which version of your API to update going forward.
+
+## How does this help?
+As a baseline, keeping a wholesale copy of the versioned API components helps lock in their behavior and protect them from change going forward. It's not a silver bullet, since unversioned dependencies (like your model, factories, and permissions) can still affect the behavior of these versioned API components, but even in that case these copied files give us a place where we can implement the logic that helps older versions of the API continue to operate even as unversioned components like our domain model continue changing.
+
+### Versioned API Tests
+By versioning our API tests, we lock in a copy of what the assumptions were for older versions of the API. Should unversioned dependencies like our domain model change in ways that break earlier versions of our API, the test suite will let us know and help us figure out when we've implemented the appropriate logic in the older version of the API controller to restore the expected behavior for that version of the API.
+
+## Advanced Topics
+
+### Object-Oriented Inheritance
+In order to reduce the surface area of legacy API controllers that you're maintaining, it might make sense in some cases to have an older versioned API controller simply inherit from a newer version or the current version of the same API controller. For example, this might make sense for endpoints that you know didn't have breaking changes across API versions.
+
+### Backporting New Features to Legacy API Versions
+Typically we'd recommend you use new feature availability to encourage existing API users to upgrade to the latest version of the API. However, in some situations you may really need to make a newer API feature available to a user who is locked into a legacy version of your API for some other endpoint. This is totally fine if the feature is only additive. For example, if you're just adding a newer API endpoint in a legacy version of the API, you can simply have the new API controller in the legacy version of the API inherit from the API controller in the current version of the API.
+
+### Pruning Unused Legacy API Endpoints
+Maintaining legacy endpoints has a very real cost, so you may choose to identify which endpoints aren't being used on legacy versions of your API and prune them from that version entirely. This has the effect of requiring existing API users to keep their API usage up-to-date before expanding the surface area of usage, which may or may not be desirable for you.

data/docs/api.md

@@ -0,0 +1,106 @@
+# REST API
+We believe every SaaS application should have an API and [webhooks](/docs/webhooks/outgoing.md) available to users, so Bullet Train aims to help automate the creation of a production-grade REST API using Rails-native tooling and provides a forward-thinking strategy for its long-term maintenance.
+
+## Background
+Vanilla Rails scaffolding actually provides simple API functionality out-of-the-box: You can append `.json` to the URL of any scaffold and it will render a JSON representation instead of an HTML view. This functionality continues to work in Bullet Train, but our API implementation also builds on this simple baseline using the same tools with additional organization and some new patterns. 
+
+## Goals
+
+### Zero-Effort API
+As with vanilla Rails scaffolding, Super Scaffolding automatically generates your API as you scaffold new models, and unlike vanilla Rails scaffolding, it will automatically keep it up-to-date as you scaffold additional attributes onto your models.
+
+### Versioning by Default
+By separating out and versioning API controllers, views, routes, and tests, Bullet Train provides [a methodology and tooling](/docs/api/versioning.md) to help ensure that once users have built against your API, changes in the structure of your domain model and API don't unexpectedly break existing integrations. You can [read more about API versioning](/docs/api/versioning.md).
+
+### Standard Rails Tooling
+APIs are built using standard Rails tools like `ActiveController::API`, [Strong Parameters](https://api.rubyonrails.org/classes/ActionController/StrongParameters.html), `config/routes.rb`, and [Jbuilder](https://github.com/rails/jbuilder). Maintaining API endpoints doesn't require special knowledge and feels like regular Rails development.
+
+### Outsourced Authentication
+In the same way we've adopted [Devise](https://github.com/heartcombo/devise) for best-of-breed and battle-tested authentication on the browser side, we've adopted [Doorkeeper](https://github.com/doorkeeper-gem/doorkeeper) for best-of-breed and battle-tested authentication on the API side.
+
+### DRY Authorization Logic
+Because our API endpoints are standard Rails controllers, they're able to leverage the exact same [permissions definitions and authorization logic](https://github.com/bullet-train-co/bullet_train-base/blob/main/docs/permissions.md) as our account controllers.
+
+## Structure
+Where vanilla Rails uses a single controller in `app/controllers` for both in-browser and API requests, Bullet Train splits these into two separate controllers, one in `app/controllers/account` and another in `app/controllers/api/v1`, although a lot of logic is shared between the two.
+
+API endpoints are defined in three parts:
+
+1. Routes are defined in `config/routes/api/v1.rb`.
+2. Controllers are defined in the `app/controllers/api/v1` directory.
+3. Jbuilder views are defined in the `app/views/api/v1` directory.
+
+## "API First" and Supporting Account Controllers
+As previously mentioned, there is a lot of shared logic between account and API controllers. Importantly, there are a couple of responsbilities that are implemented "API first" in API controllers and then utilized by account controllers.
+
+### Strong Parameters
+The primary definition of Strong Parameters for a given resource is defined in the most recent version of the API controller and included from there by the account controller. In account controllers, where you might expect to see a Strong Parameters definition, you'll see the following instead:
+
+```ruby
+include strong_parameters_from_api
+```
+
+> This may feel counter-intuitive to some developers and you might wonder why we don't flip this around and have the primary definition in the account controller and have the API controller delegate to it. The answer is a pragmatic one: creating and maintaining the defintion of Strong Paramters in the API controller means it gets automatically frozen in time should you ever need to [bump your API version number](/api/docs/versioning.md). We probably _could_ accomplish this if things were the other way around, but it wouldn't happen automatically.
+
+If by chance there are additional attributes that should be permitted or specific logic that needs to be run as part of the account controller (or inversely, only in the API controller), you can specify that in the controller like so:
+
+```ruby
+def permitted_fields
+  [:some_specific_attribute]
+end
+
+def permitted_arrays
+  {some_collection: []}
+end
+
+def process_params(strong_params)
+  assign_checkboxes(strong_params, :some_checkboxes)
+  strong_params
+end
+```
+
+### Delegating `.json` View Rendering on Account Controllers
+
+In Bullet Train, when you append `.json` to an account URL, the account controller doesn't actually have any `.json.jbuilder` templates in its view directory within `app/views/account`. Instead, by default the controller is configured to delegate the JSON rendering to the corresponding Jbuilder templates in the most recent version of the API, like so:
+
+```ruby
+# GET /account/projects/:id or /account/projects/:id.json
+def show
+  delegate_json_to_api
+end
+```
+
+## Usage Example
+First, provision a platform application in section titled "Your Applications" in the "Developers" menu of the application. When you create a new platform application, an access token that doesn't automatically expire will be automatically provisioned along with it. You can then use the access token to hit the API, as seen in the following Ruby-based example:
+
+```ruby
+require 'net/http'
+require 'uri'
+
+# Configure an API client.
+client = Net::HTTP.new('localhost', 3000)
+
+headers = {
+  "Content-Type" => "application/json",
+  "Authorization" => "Bearer GfNLkDmzOTqAacR1Kqv0VJo7ft2TT-S_p8C6zPDBFhg"
+}
+
+# Fetch the team details.
+response = client.get("/api/v1/teams/1", headers)
+
+# Parse response.
+team = JSON.parse(response.body)
+
+# Update team name.
+team["name"] = "Updated Team Name"
+
+# Push the update to the API.
+# Note that the team attributes are nested under a `team` key in the JSON body.
+response = client.patch("/api/v1/teams/1", {team: team}.to_json, headers)
+```
+
+## Advanced Topics
+ - [API Versioning](/docs/api/versioning.md)
+
+## A Note About Other Serializers and API Frameworks
+In early versions of Bullet Train we made the decision to adopt a specific serialization library, [ActiveModelSerializers](https://github.com/rails-api/active_model_serializers) and in subsequent versions we went as far as to adopt an entire third-party framework ([Grape](https://github.com/ruby-grape/grape)) and a third-party API specification ([JSON:API](https://jsonapi.org)). We now consider it out-of-scope to try and make such decisions on behalf of developers. Support for them in Bullet Train applications and in Super Scaffolding could be created by third-parties.

data/docs/index.md

@@ -40,11 +40,12 @@
  - [Stripe](/docs/billing/stripe.md)
 
 ## Integration
- - [OAuth Providers](/docs/oauth.md)
  - [REST API](/docs/api.md)
+ - [Zapier](/docs/zapier.md)
+ - [OAuth Providers](/docs/oauth.md)
  - [Outgoing Webhooks](/docs/webhooks/outgoing.md)
  - [Incoming Webhooks](/docs/webhooks/incoming.md)
-
+ 
 ## Add-Ons
  - [Font Awesome Pro](/docs/font-awesome-pro.md)
 

data/docs/zapier.md

@@ -0,0 +1,46 @@
+# Integrating with Zapier
+Bullet Train provides out-of-the-box support for Zapier. New Bullet Train projects include a preconfigured Zapier CLI project that is ready to `zapier deploy`.
+
+## Background
+Zapier was designed to take advantage of an application's existing [REST API](/docs/api.md), [outgoing webhook capabilities](/docs/webhooks/outgoing.md), and OAuth2 authorization workflows. Thankfully for us, Bullet Train provides the first two and pre-configures Doorkeeper to provide the latter. We also have an smooth OAuth2 connection workflow that accounts for the mismatch between the user-based OAuth2 standard and team-based multitenancy.
+
+## Prerequitesites
+ - You must be developing in an environment with [tunneling enabled](/docs/tunneling.md).
+
+## Getting Started in Development
+First, install the Zapier CLI tooling and deploy:
+
+```
+cd zapier
+yarn install
+zapier login
+zapier register
+zapier push
+```
+
+Once the application is registered in your account, you can re-run seeds in your development environment and it will create a `Platform::Application` record for Zapier:
+
+```
+cd ..
+rake db:seed
+```
+
+When you do this for the first time, it will output some credentials for you to go back and configure for the Zapier application, like so:
+
+```
+cd zapier
+zapier env:set 1.0.0 \
+  BASE_URL=https://andrewculver.ngrok.io \
+  CLIENT_ID=... \
+  CLIENT_SECRET=...
+cd ..
+```
+
+You're done and can now test creating Zaps that react to example objects being created or create example objects based on other triggers.
+
+## Deploying in Production
+We haven't figured out a good suggested process for breaking out development and production versions of the Zapier application yet, but we'll update this section when we have.
+
+## Future Plans
+ - Extend Super Scaffolding to automatically add new resources to the Zapier CLI project. For now you have to extend the Zapier CLI definitions manually.
+

data/lib/bullet_train/version.rb

@@ -1,3 +1,3 @@
 module BulletTrain
-  VERSION = "1.2.5"
+  VERSION = "1.2.7"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: bullet_train
 version: !ruby/object:Gem::Version
-  version: 1.2.5
+  version: 1.2.7
 platform: ruby
 authors:
 - Andrew Culver
@@ -626,6 +626,8 @@ files:
 - db/migrate/20211020200855_add_doorkeeper_application_to_memberships.rb
 - db/migrate/20211027002944_add_doorkeeper_application_to_users.rb
 - docs/action-models.md
+- docs/api.md
+- docs/api/versioning.md
 - docs/application-options.md
 - docs/authentication.md
 - docs/billing/stripe.md
@@ -662,6 +664,7 @@ files:
 - docs/upgrades.md
 - docs/webhooks/incoming.md
 - docs/webhooks/outgoing.md
+- docs/zapier.md
 - lib/bullet_train.rb
 - lib/bullet_train/core_ext/string_emoji_helper.rb
 - lib/bullet_train/engine.rb