bullet_train 1.0.46 → 1.0.47

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 9e6c930c4e6fad0f50e6869cdfcceec0b40ac27e4eef3dc04facde80918c9276
-  data.tar.gz: bf9576a58a7c27ac23b46fbacbf93b16a4ac03bae5abc573ffc468e6dce11dc5
+  metadata.gz: c4a10e169bed7e2cc9dfef7fe304ff60ab66a1eecceb50129ca616c1c7b390f7
+  data.tar.gz: 5370e36c4d668fe9282abb1c3c6d9552bd6351eb045a646ad388f74bc83e49b5
 SHA512:
-  metadata.gz: 9b6f9ce718307c62a69e49faf9948ba43b1fad9269c49b8562683c9deff3f7c00595d5d0216e2d01bf8b0a25a619164d8e48ca37570b0cbace136ec23fa9b7e3
-  data.tar.gz: 534d607fb41150372dcaea0af84b8aa8fa5897c1af3bf6bab4019cfbb06bf565819a543896dd131b081c39c7081b89144159f42e0118278a304ffd21bd745760
+  metadata.gz: 341306e5e082f27c17a1240a156b7680e0fb150d21dcf1621bbca7f273af8560f17b131742022b10b0a29ceb8dd5af9d82f037bea24a11bff50b6ecbc0ee2165
+  data.tar.gz: 14a518a963da1f8f122ceb2ba332f6839f5cc92d23b147820c57dba59554a4241a9224e1760729710a29770792c83d5d0deffc6c68fc05c885701d816799ef4b

data/README.md

@@ -13,12 +13,12 @@ gem "bullet_train"
 
 And then execute:
 ```bash
-$ bundle
+bundle
 ```
 
 Or install it yourself as:
 ```bash
-$ gem install bullet_train
+gem install bullet_train
 ```
 
 ## Contributing

data/docs/authentication.md

@@ -5,8 +5,8 @@ Bullet Train uses [Devise](https://github.com/heartcombo/devise) for authenticat
 Bullet Train registers its own slightly customized registration and session controllers for Devise. If you want to customize them further, you can simply eject those controllers from the framework and override them locally, like so:
 
 ```
-$ bin/resolve RegistrationsController --eject --open
-$ bin/resolve SessionsController --eject --open
+bin/resolve RegistrationsController --eject --open
+bin/resolve SessionsController --eject --open
 ```
 
 ## Customizing Views

data/docs/getting-started.md

@@ -11,45 +11,45 @@ If you're using Bullet Train for the first time, begin by learning these five im
 1. Use `rails g model` to create and `bin/super-scaffold` to scaffold a new model:
 
     ```
-    $ rails g model Project team:references name:string
-    $ bin/super-scaffold crud Project Team name:text_field
+    rails g model Project team:references name:string
+    bin/super-scaffold crud Project Team name:text_field
     ```
 
-    In this example, `Team` refers to the immediate parent of the `Project` resource. For more details, just run `bin/super-scaffold` or [read the documentation](https://github.com/bullet-train-co/bullet_train-base/blob/main/docs/super-scaffolding.md).
+    In this example, `Team` refers to the immediate parent of the `Project` resource. For more details, just run `bin/super-scaffold` or [read the documentation](/docs/super-scaffolding.md).
 
 2. Use `rails g migration` and `bin/super-scaffold` to add a new field to a model you've already scaffolded:
 
     ```
-    $ rails g migration add_description_to_projects description:text
-    $ bin/super-scaffold crud-field Project description:trix_editor
+    rails g migration add_description_to_projects description:text
+    bin/super-scaffold crud-field Project description:trix_editor
     ```
 
-    These first two points about Super Scaffolding are just the tip of the iceberg, so be sure to circle around and [read the full documentation](https://github.com/bullet-train-co/bullet_train-base/blob/main/docs/super-scaffolding.md).
+    These first two points about Super Scaffolding are just the tip of the iceberg, so be sure to circle around and [read the full documentation](/docs/super-scaffolding.md).
 
 3. Figure out which ERB views are powering something you see in the UI by:
 
     - Right clicking the element.
     - Selecting "Inspect Element".
-    - Looking for the `<!--XRAY START ...-->` comment above the element you've selected.
+    - Looking for the `<!-- BEGIN ... -->` comment above the element you've selected.
 
 4. Figure out the full I18N translation key of any string on the page by adding `?show_locales=true` to the URL.
 
 5. Use `bin/resolve` to figure out where framework or theme things are coming from and eject them if you need to customize something locally:
 
     ```
-    $ bin/resolve Users::Base
-    $ bin/resolve en.account.teams.show.header --open
-    $ bin/resolve shared/box --open --eject
+    bin/resolve Users::Base
+    bin/resolve en.account.teams.show.header --open
+    bin/resolve shared/box --open --eject
     ```
 
     Also, for inputs that can't be provided on the shell, there's an interactive mode where you can paste them:
 
     ```
-    $ bin/resolve --interactive --eject --open
+    bin/resolve --interactive --eject --open
     ```
 
     And then paste any input, e.g.:
 
     ```
-    <!--XRAY START 73 /Users/andrewculver/.rbenv/versions/3.1.1/lib/ruby/gems/3.1.0/gems/bullet_train-themes-light-1.0.10/app/views/themes/light/commentary/_box.html.erb-->
+    <!-- BEGIN /Users/andrewculver/.rbenv/versions/3.1.1/lib/ruby/gems/3.1.0/gems/bullet_train-themes-light-1.0.10/app/views/themes/light/commentary/_box.html.erb -->
     ```

data/docs/indirection.md

@@ -27,20 +27,18 @@ Even in vanilla Rails development, when you're looking at a view file, the path
 `bin/resolve` makes it easy to figure out where where a partial is being served from:
 
 ```
-$ bin/resolve shared/box
+bin/resolve shared/box
 ```
 
-### Exposing Rendered Views with Xray
+### Exposing Rendered Views with Annotated Views
 
-> TODO Is this still true in Rails 7? Does it not do something like this by default now?
-
-If you're looking at a rendered view in the browser, it can be hard to know which file to open in order to make a change. To help, Bullet Train includes [Xray](https://github.com/brentd/xray-rails) by default, so you can right click on any element you see, select "Inspect Element", and you'll see comments in the HTML source telling you which file is powering a particular portion of the view, like this:
+If you're looking at a rendered view in the browser, it can be hard to know which file to open in order to make a change. To help, Bullet Train enables `config.action_view.annotate_rendered_view_with_filenames` by default, so you can right click on any element you see, select "Inspect Element", and you'll see comments in the HTML source telling you which file is powering a particular portion of the view, like this:
 
 ```
-<!--XRAY START 90 /Users/andrewculver/.rbenv/versions/3.1.1/lib/ruby/gems/3.1.0/gems/bullet_train-themes-light-1.0.10/app/views/themes/light/workflow/_box.html.erb-->
+<!-- BEGIN /Users/andrewculver/.rbenv/versions/3.1.1/lib/ruby/gems/3.1.0/gems/bullet_train-themes-light-1.0.10/app/views/themes/light/workflow/_box.html.erb -->
 ```
 
-Note that in the example above, the view in question isn't actually coming from the application repository. Instead, it's being included from the `bullet_train-themes-light` package. For instructions on how to customize it, see [Overriding the Framework](/docs/override).
+Note that in the example above, the view in question isn't actually coming from the application repository. Instead, it's being included from the `bullet_train-themes-light` package. For instructions on how to customize it, see [Overriding Framework Defaults](/docs/overriding.md).
 
 ### Drilling Down on Translation Keys
 
@@ -59,5 +57,5 @@ You can also log all the translation key for anything being rendered to the cons
 Once you have the full I18N translation key, you can use `bin/resolve` to figure out which package and file it's coming from. At that point, if you need to customize it, you can also use the `--eject` option to copy the  the framework for customization in your local application:
 
 ```
-$ bin/resolve en.account.onboarding.user_details.edit.header --eject --open
+bin/resolve en.account.onboarding.user_details.edit.header --eject --open
 ```

data/docs/namespacing.md

@@ -7,5 +7,5 @@ Bullet Train comes preconfigured with an `Account` and controller and view names
 In Bullet Train applications with [multiple team types](/docs/teams.md), you may find it helpful to introduce additional controller and view namespaces to represent and organize user interfaces and experiences for certain team types that vary substantially from the `Account` namespace default. In Super Scaffolding, you can specify a namespace other than `Account` with the `--namespace` option, for example:
 
 ```
-$ bin/super-scaffold crud Event Team name:text_field --namespace=customers
+bin/super-scaffold crud Event Team name:text_field --namespace=customers
 ```

data/lib/bullet_train/resolver.rb

@@ -126,11 +126,11 @@ module BulletTrain
     end
 
     def partial_path
-      xray_path = ApplicationController.render(template: "bullet_train/partial_resolver", layout: nil, assigns: {needle: @needle}).lines[1].chomp
-      if xray_path =~ /<!--XRAY START \d+ (.*)-->/
+      annotated_path = ApplicationController.render(template: "bullet_train/partial_resolver", layout: nil, assigns: {needle: @needle}).lines[1].chomp
+      if annotated_path =~ /<!-- BEGIN (.*) -->/
         $1
       else
-        raise "It looks like Xray-rails isn't properly enabled?"
+        raise "It looks like `config.action_view.annotate_rendered_view_with_filenames` isn't enabled?"
       end
     rescue ActionView::Template::Error => _
       nil

data/lib/bullet_train/version.rb

@@ -1,3 +1,3 @@
 module BulletTrain
-  VERSION = "1.0.46"
+  VERSION = "1.0.47"
 end

data/lib/tasks/bullet_train_tasks.rake

@@ -42,8 +42,8 @@ namespace :bullet_train do
       input = $stdin.gets.strip
       $stdin.getc while $stdin.ready?
 
-      # Extract absolute paths from XRAY comments.
-      if input =~ /<!--XRAY START \d+ (.*)-->/
+      # Extract absolute paths from annotated views.
+      if input =~ /<!-- BEGIN (.*) -->/
         input = $1
       end
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: bullet_train
 version: !ruby/object:Gem::Version
-  version: 1.0.46
+  version: 1.0.47
 platform: ruby
 authors:
 - Andrew Culver
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2022-04-02 00:00:00.000000000 Z
+date: 2022-04-04 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: standard