bullet_train 1.2.27 → 1.3.1

data/docs/super-scaffolding/delegated-types.md

@@ -48,7 +48,7 @@ We use `entryable_type:buttons` because we're going to allow people to choose wh
 
 Super Scaffolding will have generated some initial button options for us already in `config/locales/en/entries.en.yml`. We'll want to update the attribute `name`, field `label` (which is shown on the form) and the available options to reflect the available Concrete Children like so:
 
-```
+```yaml
 fields: &fields
   entryable_type:
     name: &entryable_type Entry Type
@@ -61,7 +61,7 @@ fields: &fields
 
 We will add this block below in the next step on our `new.html.erb` page so you don't have to worry about it now, but with the options above in place, our buttons partial will now allow your users to select either a `Message` or a `Comment` before creating the `Entry` itself:
 
-```
+```erb
 <% with_field_settings form: form do %>
   <%= render 'shared/fields/buttons', method: :entryable_type, html_options: {autofocus: true} %>
   <%# 🚅 super scaffolding will insert new fields above this line. %>
@@ -69,7 +69,8 @@ We will add this block below in the next step on our `new.html.erb` page so you
 ```
 
 This will produce the following HTML:
-```
+
+```html
 <div>
   <label class="btn-toggle" data-controller="fields--button-toggle">
     <input data-fields--button-toggle-target="shadowField" type="radio" value="Message" name="entry[entryable_type]" id="entry_entryable_type_message">
@@ -91,7 +92,7 @@ This will produce the following HTML:
 
 By default, `app/views/account/entries/new.html.erb` has this reference to the shared `_form.html.erb`:
 
-```
+```erb
 <%= render 'form', entry: @entry %>
 ```
 
@@ -102,7 +103,7 @@ However, in this workflow we actually need two steps:
 
 The first of these two forms is actually not shared between `new.html.erb` and `edit.html.erb`, so we'll copy the contents of `_form.html.erb` into `new.html.erb` as a starting point, like so:
 
-```
+```erb
 <% if @entry.entryable_type %>
   <%= render 'form', entry: @entry %>
 <% else %>
@@ -131,14 +132,14 @@ Here's a summary of the updates required when copying `_form.html.erb` into `new
 
 We need to add a locale entry for the "Next Step" button in `config/locales/en/entries.en.yml`. This goes under the `buttons: &buttons` entry that is already present, like so:
 
-```
+```yaml
 buttons: &buttons
   next: Next Step
 ```
 
 Also, sadly, the original locale file wasn't expecting any buttons in `new.html.erb` directly, so we need to include buttons on the `new` page in the same file, below `form: *form`, like so:
 
-```
+```yaml
 new:
   # ...
   form: *form
@@ -149,7 +150,7 @@ new:
 
 In `app/models/entry.rb`, we want to replace the default validation of `entryable_type` like so:
 
-```
+```ruby
 ENTRYABLE_TYPES = I18n.t('entries.fields.entryable_type.options').keys.map(&:to_s)
 
 validates :entryable_type, inclusion: {
@@ -163,7 +164,7 @@ This makes the locale file, where we define the options to present to the user,
 
 Also, to make it easy to check the state of this validation, we'll add `entryable_type_valid?` as well:
 
-```
+```ruby
 def entryable_type_valid?
   ENTRYABLE_TYPES.include?(entryable_type)
 end
@@ -177,13 +178,13 @@ In preparation for the second step, we need to configure `Entry` to accept [nest
 
 In `app/models/entry.rb`, like so:
 
-```
+```ruby
 accepts_nested_attributes_for :entryable
 ```
 
 Also in `app/models/entry.rb`, [Rails will be expecting us](https://stackoverflow.com/questions/45295202/cannot-build-nested-polymorphic-associations-are-you-trying-to-build-a-polymor) to define the following method on the model:
 
-```
+```ruby
 def build_entryable(params = {})
   raise 'invalid entryable type' unless entryable_type_valid?
   self.entryable = entryable_type.constantize.new(params)
@@ -192,13 +193,13 @@ end
 
 Finally, in the [strong parameters](https://edgeguides.rubyonrails.org/action_controller_overview.html#strong-parameters) of `app/controllers/account/entries_controller.rb`, _directly below_ this line:
 
-```
+```ruby
 # 🚅 super scaffolding will insert new arrays above this line.
 ```
 
 And still within the `permit` parameters, add:
 
-```
+```ruby
 entryable_attributes: [
   :id,
 
@@ -216,7 +217,7 @@ entryable_attributes: [
 
 Before we can present the second step to users, we need to react to the user's input from the first step and initialize either a `Message` or `Comment` object and associate `@entry` with it. We do this in the `new` action of `app/controllers/account/entries_controller.rb` and we can also use the `build_entryable` method we created earlier for this purpose, like so:
 
-```
+```ruby
 def new
   if @entry.entryable_type_valid?
     @entry.build_entryable
@@ -230,19 +231,19 @@ end
 
 Since we're now prompting for the entry type on the first step, we can remove the following from the second step in `app/views/account/entries/_form.html.erb`:
 
-```
+```erb
 <%= render 'shared/fields/buttons', method: :entryable_type, html_options: {autofocus: true} %>
 ```
 
 But we need to keep track of which entry type they selected, so we replace it with:
 
-```
+```erb
 <%= form.hidden_field :entryable_type %>
 ```
 
 Also, below that (and below the Super Scaffolding hook), we want to add the `Message` and `Comment` fields as [nested forms](https://guides.rubyonrails.org/form_helpers.html#nested-forms) like so:
 
-```
+```erb
 <%= form.fields_for :entryable, entry.entryable do |entryable_form| %>
   <%= entryable_form.hidden_field :id %>
   <% with_field_settings form: entryable_form do %>
@@ -262,7 +263,7 @@ We add this _below_ the Super Scaffolding hook because we want any additional fi
 
 Add the following in `app/views/account/entries/show.html.erb` under the Super Scaffolding hook shown in the example code below:
 
-```
+```erb
 <%# 🚅 super scaffolding will insert new fields above this line. %>
 
 <% with_attribute_settings object: @entry.entryable, strategy: :label do %>
@@ -278,7 +279,8 @@ Add the following in `app/views/account/entries/show.html.erb` under the Super S
 This will ensure the various different attributes of the Concrete Children are properly presented. However, the `label` strategy for these attribute partials depend on the locales for the individual Concrete Children being defined, so we need to create those files now, as well:
 
 `config/locales/en/messages.en.yml`:
-```
+
+```yaml
 en:
   messages: &messages
     fields:
@@ -295,7 +297,8 @@ en:
 ```
 
 `config/locales/en/comments.en.yml`:
-```
+
+```yaml
 en:
   comments: &comments
     fields:
@@ -323,19 +326,19 @@ So everything should now be working as expected, and here's the crazy thing: **W
 
 To now incorporate delegated types as put forward in the original documentation, we want to remove this line in `app/models/entry.rb`:
 
-```
+```ruby
 belongs_to :entryable, polymorphic: true
 ```
 
 And replace it with:
 
-```
+```ruby
 delegated_type :entryable, types: %w[ Message Comment ]
 ```
 
 We also want to follow the other steps seen there, such as defining an `Entryable` concern in `app/models/concerns/entryable.rb`, like so:
 
-```
+```ruby
 module Entryable
   extend ActiveSupport::Concern
 
@@ -347,7 +350,7 @@ end
 
 And including the `Entryable` concern in both `app/models/message.rb` and `app/models/comment.rb` like so:
 
-```
+```ruby
 include Entryable
 ```
 

data/docs/super-scaffolding/options.md

@@ -0,0 +1,24 @@
+# Super Scaffolding Options
+
+There are different flags you can pass to the Super Scaffolding command which gives you more flexibility over creating your model. Add the flag of your choice to **the end** of the command for the option to take effect.
+```
+bin/super-scaffold crud Project Team description:text_field --sortable
+```
+
+Most of these include skipping particular functionalities, so take a look at what's available here and pass the flag that applies to your use-case.
+
+| Option | Description |
+|--------|-------------|
+| `--sortable` | [Details here](/docs/super-scaffolding/sortable.md) |
+| `--namespace=customers` | [Details here](/docs/namespacing.md) |
+| `--sidebar="ti-world"` | Pass the Themify icon or Font Awesome icon of your choice to automatically add it to the navbar* |
+| `--only-index` | Only scaffold the index view for a model"` |
+| `--skip-views` | |
+| `--skip-form` | |
+| `--skip-locales` | |
+| `--skip-api` | |
+| `--skip-model` | |
+| `--skip-controller` | |
+| `--skip-routes` | |
+
+*This option is only available for top-level models, which are models that are direct children of the `Team` model.

data/docs/super-scaffolding/sortable.md

@@ -5,7 +5,7 @@ When issuing a `bin/super-scaffold crud` command, you can pass the `--sortable`
 ```
 # E.g. Pages belong to a Site and are sortable via drag-and-drop:
 rails g model Page site:references name:string path:text
-bin/super-scaffold crud Page Site,Team name:text path:text --sortable
+bin/super-scaffold crud Page Site,Team name:text_field path:text_area --sortable
 ```
 
 The `--sortable` option:

data/docs/super-scaffolding.md

@@ -130,7 +130,7 @@ bin/super-scaffold crud-field Project status:buttons
 
 By default, Super Scaffolding configures the buttons as "One", "Two", and "Three", but in this example you can edit those options in the `fields` section of `config/locales/en/projects.en.yml`. For example, you could specify the following options:
 
-```
+```yaml
 planned: Planned
 started: Started
 completed: Completed
@@ -138,7 +138,7 @@ completed: Completed
 
 If you want new `Project` models to be set to `planned` by default, you can add that to the migration file that was generated before running it, like so:
 
-```
+```ruby
 add_column :projects, :status, :string, default: "planned"
 ```
 
@@ -170,7 +170,7 @@ There are two important things to point out here:
 
 Finally, Super Scaffolding will prompt you to edit `app/models/project.rb` and implement the required logic in the `valid_leads` method. This is a template method that will be used to both populate the select field on the `Project` form, but also enforce some important security concerns in this multi-tenant system. In this case, you can define it as:
 
-```
+```ruby
 def valid_leads
   team.memberships.current_and_invited
 end
@@ -220,7 +220,7 @@ Just note that the suffix of the field is `_ids` plural, and this is an attribut
 
 The `crud-field` step will ask you to define the logic for the `valid_tags` method in `app/models/project.rb`. You can define it like so:
 
-```
+```ruby
 def valid_tags
   team.projects_tags
 end
@@ -245,10 +245,11 @@ Only the files associated with `Scaffolding::CompletelyConcrete::TangibleThing`
 
 You won't want your end users seeing the Super Scaffolding templates in your environment, so you can disable their presentation by setting `HIDE_THINGS` in your environment. For example, you can add the following to `config/application.yml`:
 
-```
+```yaml
 HIDE_THINGS: true
 ```
 
 ## Advanced Examples
+ - [Super Scaffolding Options](/docs/super-scaffolding/options.md)
  - [Super Scaffolding with Delegated Types](/docs/super-scaffolding/delegated-types.md)
- - [Super Scaffolding with the `--sortable` option](/docs/super-scaffolding/sortable.md)
+ - [Super Scaffolding with the `--sortable` option](/docs/super-scaffolding/sortable.md)

data/docs/testing.md

@@ -14,7 +14,7 @@ rails test:system
 
 When debugging tests, it's important to be able to see what Capybara is seeing. You can disable the headless browser mode by prefixing `rails test` like so:
 
-```
+```shell
 MAGIC_TEST=1 rails test
 ```
 

data/docs/themes.md

@@ -25,7 +25,7 @@ You can also pass an annotated path to a view after running `bin/resolve --inter
 
 To use a theme component, simply include it from "within" `shared` like so:
 
-```
+```erb
 <%= render 'shared/fields/text_field', method: :text_field_value %>
 ```
 
@@ -40,7 +40,7 @@ This small piece of indirection buys us an incredible amount of power in buildin
 Your application will automatically be configured to use your new theme whenever you run the eject command. You can run the below command to re-install the standard light theme.
 ```
 > rake bullet_train:themes:light:install
-``` 
+```
 
 ## Additional Guidance and Principles
 
@@ -56,7 +56,7 @@ On the other hand, if you decide to try to build a theme from the ground up, you
 
 #### ❌ Don’t do this, even in theme partials:
 
-```
+```erb
 <%= render "themes/light/box" do |p| %>
   ...
 <% end %>
@@ -64,7 +64,7 @@ On the other hand, if you decide to try to build a theme from the ground up, you
 
 #### ✅ Instead, always do this:
 
-```
+```erb
 <%= render "shared/box" do |p| %>
   ...
 <% end %>

data/docs/tunneling.md

@@ -4,7 +4,7 @@ Before your application can take advantage of features that depend on incoming w
 
 ## Use a Paid Plan
 
-You should specifically sign up for a paid account. Although ngrok offers a free plan, their $25/month paid plan will allow you to reserve a custom subdomain for reuse each time you spin up your tunnel. This is a critical productivity improvement, because in practice you'll end up configuring your tunnel URL in a bunch of different places like `config/application.yml` but also in external systems like when you [configure payment providers to deliver webhooks to you](/docs/billing/stripe.md).
+You should specifically sign up for a paid account. Although ngrok offers a free plan, their $8/year or $10/month [paid plan](https://ngrok.com/pricing) will allow you to reserve a custom subdomain for reuse each time you spin up your tunnel. This is a critical productivity improvement, because in practice you'll end up configuring your tunnel URL in a bunch of different places like `config/application.yml` but also in external systems like when you [configure payment providers to deliver webhooks to you](/docs/billing/stripe.md).
 
 ## Usage
 
@@ -18,7 +18,7 @@ ngrok http 3000 --subdomain=YOUR-SUBDOMAIN
 
 Before your Rails application will accept connections on your tunnel hostname, you need to update `config/application.yml` with:
 
-```
+```yaml
 BASE_URL: https://YOUR-SUBDOMAIN.ngrok.io
 ```
 

data/docs/upgrades.md

@@ -27,20 +27,20 @@ git clean -d -f
 ### 2. Fetch the latest and greatest from the Bullet Train repository.
 
 ```
-git fetch starter-repo
-````
+git fetch bullet-train
+```
 
 ### 3. Create a new "upgrade" branch off of your main branch.
 
 ```
 git checkout main
-git checkout -b updating-starter-repo
+git checkout -b updating-bullet-train
 ```
 
 ### 4. Merge in the newest stuff from Bullet Train and resolve any merge conflicts.
 
 ```
-git merge starter-repo/main
+git merge bullet-train/main
 ```
 
 It's quite possible you'll get some merge conflicts at this point. No big deal! Just go through and resolve them like you would if you were integrating code from another developer on your team. We tend to comment our code heavily, but if you have any questions about the code you're trying to understand, let us know on Discord!
@@ -62,9 +62,9 @@ rails test:system
 
 ```
 git checkout main
-git merge updating-starter-repo
+git merge updating-bullet-train
 git push origin main
-git branch -d updating-starter-repo
+git branch -d updating-bullet-train
 ```
 
-Alternatively, if you're using GitHub, you can push the `updating-starter-repo` branch up and create a PR from it and let your CI integration do it's thing and then merge in the PR and delete the branch there. (That's what we typically do.)
+Alternatively, if you're using GitHub, you can push the `updating-bullet-train` branch up and create a PR from it and let your CI integration do it's thing and then merge in the PR and delete the branch there. (That's what we typically do.)

data/docs/zapier.md

@@ -4,7 +4,7 @@ Bullet Train provides out-of-the-box support for Zapier. New Bullet Train projec
 ## 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 a smooth OAuth2 connection workflow that accounts for the mismatch between user-based OAuth2 and team-based multitenancy.
 
-## Prerequitesites
+## Prerequisites
  - You must be developing in an environment with [tunneling enabled](/docs/tunneling.md).
 
 ## Getting Started in Development

data/lib/bullet_train/configuration.rb

@@ -1,15 +1,21 @@
 module BulletTrain
   class Configuration
+    include Singleton
     attr_accessor :strong_passwords
 
-    @default = Configuration.new
+    @@config = nil
 
     def initialize
-      self.strong_passwords = true
+      @@config = self
+
+      # Default values
+      @strong_passwords = true
     end
 
     class << self
-      attr_reader :default
+      def strong_passwords
+        @@config&.strong_passwords
+      end
     end
   end
 end

data/lib/bullet_train/resolver.rb

@@ -75,7 +75,7 @@ module BulletTrain
 
           # TODO: Use TerminalCommands to open this file
           open_command = `which open`.present? ? "open" : "xdg-open"
-          exec "#{open_command} #{path}"
+          exec "#{open_command} #{source_file[:absolute_path]}"
         end
       else
         puts "Couldn't resolve `#{@needle}`.".red
@@ -89,22 +89,27 @@ module BulletTrain
         package_name: nil,
       }
 
-      result[:absolute_path] = file_path || class_path || partial_path || locale_path
+      result[:absolute_path] = file_path || class_path || locale_path || partial_path
 
       # If we get the partial resolver template itself, that means we couldn't find the file.
-      if result[:absolute_path].match?("app/views/bullet_train/partial_resolver.html.erb")
-        puts "We could not find the partial you're looking for: #{@needle}".red
+      if result[:absolute_path].match?("app/views/bullet_train/partial_resolver.html.erb") || result[:absolute_path].nil?
+        puts "We could not resolve the value you're looking for: #{@needle}".red
         puts ""
-        puts "Please try passing the partial string using either of the following two ways:"
+        puts "If you're looking for a partial, please try passing the partial string in either of the following two ways:"
         puts "1. Without underscore and extention: ".blue + "bin/resolve shared/attributes/code"
         puts "2. Literal path with package name: ".blue + "bin/resolve bullet_train-themes/app/views/themes/base/attributes/_code.html.erb"
         puts ""
+        puts "If you're looking for a locale, the key might not be implemented yet."
+        puts "Try adding your own custom text for the key to your locale file and try again."
         exit
       end
 
       if result[:absolute_path]
         if result[:absolute_path].include?("/bullet_train")
-          regex = /#{"bullet_train-core" if result[:absolute_path].include?("bullet_train-core")}\/bullet_train[a-z|\-._0-9]*.*/
+          # This Regular Expression covers gem versions like bullet_train-1.2.26,
+          # and hashed versions of branches on GitHub like bullet_train-core-b00a02bd513c.
+          gem_version_regex = /[a-z|\-._0-9]*/
+          regex = /#{"bullet_train-core#{gem_version_regex}" if result[:absolute_path].include?("bullet_train-core")}\/bullet_train#{gem_version_regex}.*/
           base_path = result[:absolute_path].scan(regex).pop
 
           # Try to calculate which package the file is from, and what it's path is within that project.

data/lib/bullet_train/version.rb

@@ -1,3 +1,3 @@
 module BulletTrain
-  VERSION = "1.2.27"
+  VERSION = "1.3.1"
 end

data/lib/bullet_train.rb

@@ -42,11 +42,8 @@ module BulletTrain
   mattr_accessor :base_class, default: "ApplicationRecord"
 
   def self.configure
-    if block_given?
-      yield(BulletTrain::Configuration.default)
-    else
-      BulletTrain::Configuration.default
-    end
+    config = BulletTrain::Configuration.instance
+    yield(config) if block_given?
   end
 end
 
@@ -82,7 +79,7 @@ def inbound_email_enabled?
 end
 
 def billing_enabled?
-  defined?(BulletTrain::Billing)
+  ENV["STRIPE_SECRET_KEY"].present? && defined?(BulletTrain::Billing)
 end
 
 # TODO This should be in an initializer or something.
@@ -104,12 +101,20 @@ def webhooks_enabled?
   true
 end
 
+def hide_things?
+  ActiveModel::Type::Boolean.new.cast(ENV["HIDE_THINGS"])
+end
+
+def hide_examples?
+  ActiveModel::Type::Boolean.new.cast(ENV["HIDE_EXAMPLES"])
+end
+
 def scaffolding_things_disabled?
-  ENV["HIDE_THINGS"].present? || ENV["HIDE_EXAMPLES"].present?
+  hide_things? || hide_examples?
 end
 
 def sample_role_disabled?
-  ENV["HIDE_EXAMPLES"].present?
+  hide_examples?
 end
 
 def demo?

data/lib/tasks/bullet_train_tasks.rake

@@ -40,11 +40,14 @@ namespace :bullet_train do
       puts "\nOK, paste what you've got for us and hit <Return>!\n".blue
 
       input = $stdin.gets.strip
+      # we only resolve the first line of user input and ignore the rest
       $stdin.getc while $stdin.ready?
 
       # Extract absolute paths from annotated views.
       if input =~ /<!-- BEGIN (.*) -->/
         input = $1
+      elsif input =~ /<!-- END (.*) -->/
+        input = $1
       end
 
       # Append the main application's path if the file is a local file.
@@ -72,6 +75,33 @@ namespace :bullet_train do
     end
   end
 
+  desc "Eject files from the Bullet Train's core logic to your application."
+  task :eject, [:type] => :environment do |task, args|
+    if args[:type] == "locales"
+      gem_names = I18n.t("framework_packages").map { |key, value| key.to_s }
+      gem_names.each do |gem|
+        puts "Searching for locales in #{gem}...".blue
+        gem_path = `bundle show #{gem}`.chomp
+        locales = Dir.glob("#{gem_path}/**/config/locales/**/*.yml").reject { |path| path.match?("dummy") }
+        next if locales.empty?
+
+        puts "Found locales. Ejecting to your application...".green
+        locales.each do |locale|
+          relative_path = locale.split("/config/locales").pop
+          path_parts = relative_path.split("/")
+          base_path = path_parts.join("/")
+          FileUtils.mkdir_p("./config/locales#{base_path}") unless Dir.exist?("./config/locales#{base_path}")
+
+          unless File.exist?("config/locales#{relative_path}")
+            puts "Ejecting #{relative_path}..."
+            File.new("config/locales#{relative_path}", "w")
+            `cp #{locale} config/locales#{relative_path}`
+          end
+        end
+      end
+    end
+  end
+
   task :hack, [:all_options] => :environment do |t, arguments|
     def stream(command, prefix = "  ")
       puts ""

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: bullet_train
 version: !ruby/object:Gem::Version
-  version: 1.2.27
+  version: 1.3.1
 platform: ruby
 authors:
 - Andrew Culver
-autorequire:
+autorequire: 
 bindir: bin
 cert_chain: []
-date: 2023-07-27 00:00:00.000000000 Z
+date: 2023-08-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: standard
@@ -164,6 +164,20 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: '0'
+- !ruby/object:Gem::Dependency
+  name: image_processing
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
 - !ruby/object:Gem::Dependency
   name: cancancan
   requirement: !ruby/object:Gem::Requirement
@@ -481,7 +495,6 @@ extra_rdoc_files: []
 files:
 - ".bt-link"
 - MIT-LICENSE
-- README.md
 - Rakefile
 - app/assets/config/bullet_train_manifest.js
 - app/controllers/account/invitations_controller.rb
@@ -609,6 +622,7 @@ files:
 - app/views/layouts/devise.html.erb
 - app/views/layouts/docs.html.erb
 - app/views/layouts/mailer.html.erb
+- app/views/layouts/public.html.erb
 - app/views/public/home/docs.html.erb
 - app/views/showcase/engine/_stylesheets.html.erb
 - app/views/user_mailer/invited.html.erb
@@ -667,6 +681,7 @@ files:
 - docs/action-models.md
 - docs/api.md
 - docs/api/versioning.md
+- docs/application-hash.md
 - docs/application-options.md
 - docs/authentication.md
 - docs/billing/stripe.md
@@ -674,6 +689,7 @@ files:
 - docs/desktop.md
 - docs/field-partials.md
 - docs/field-partials/buttons.md
+- docs/field-partials/date-related-fields.md
 - docs/field-partials/file-field.md
 - docs/field-partials/super-select.md
 - docs/font-awesome-pro.md
@@ -692,6 +708,7 @@ files:
 - docs/seeds.md
 - docs/super-scaffolding.md
 - docs/super-scaffolding/delegated-types.md
+- docs/super-scaffolding/options.md
 - docs/super-scaffolding/sortable.md
 - docs/teams.md
 - docs/testing.md
@@ -710,12 +727,12 @@ files:
 - lib/bullet_train/version.rb
 - lib/colorizer.rb
 - lib/tasks/bullet_train_tasks.rake
-homepage: https://github.com/bullet-train-co/bullet_train
+homepage: https://github.com/bullet-train-co/bullet_train-core/tree/main/bullet_train
 licenses:
 - MIT
 metadata:
-  homepage_uri: https://github.com/bullet-train-co/bullet_train
-  source_code_uri: https://github.com/bullet-train-co/bullet_train
+  homepage_uri: https://github.com/bullet-train-co/bullet_train-core/tree/main/bullet_train
+  source_code_uri: https://github.com/bullet-train-co/bullet_train-core/tree/main/bullet_train
 post_install_message: |2
       If you're upgrading `bullet_train-*` Ruby gems and you run into any new
       issues, you should probably also pull in updates from the Bullet Train
@@ -737,7 +754,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubygems_version: 3.4.10
-signing_key:
+signing_key: 
 specification_version: 4
 summary: Bullet Train
 test_files: []