bullet_train 1.33.0 → 1.34.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 46fec3f6437afa98558519d9d3c78c8d62ef76f98adf20489fa86fbdddea4360
4
- data.tar.gz: f736adc2b99e130132e29ca2490b8b5769c3561f9cdf712f8a52f7cdd3d872ed
3
+ metadata.gz: f74254bfbcc983a2ed2fbdab69dbaa872dc49a86f5a73e7b8b43e7878f2e1ae4
4
+ data.tar.gz: b5bbc3302df6e353bd86535087317b562bbba274e943fed5b9edf0e47cb3a62e
5
5
  SHA512:
6
- metadata.gz: 7cdafd0a4582cec14721c4363f8372639e232168eabd10dd4ead60876c157a18b445eb29049bf8bd4acaa3bbf216a24a04a9669c1a940013f65bdd490d9a8acf
7
- data.tar.gz: 3892477bdaa2174461dae69f6b78e947460e7cb3b263c85b1c2d920ada30486d1c587e043f0e6429eb90db90fd920e81c5778242457c4369afd7123787b79c7e
6
+ metadata.gz: 544b025b243fc8f09b4e710258481715e6276e98a061f6256687aa90777ff88b15e9da2b17b29f485c49be5c78016797c7022ae9494f3503b313fa670f0b7666
7
+ data.tar.gz: 14c932887fdaf6c184da191f638be7b46f48cc18fd897f700a5b4c8646c804d21ad8ef4952af0c59e81349361777f8d384f1c1c7deeaaeb33d82d548b90e50d0
@@ -1,7 +1,7 @@
1
1
  <tr data-id="<%= membership.id %>">
2
2
  <td class="px-6 py-4 whitespace-nowrap">
3
3
  <%= link_to [:account, membership], class: 'block flex items-center group hover:no-underline no-underline' do %>
4
- <div class="flex-shrink-0 h-10 w-10">
4
+ <div class="shrink-0 h-10 w-10">
5
5
  <%= image_tag membership_profile_photo_url(membership), title: membership.label_string, class: 'h-10 w-10 rounded-full' %>
6
6
  </div>
7
7
 
@@ -24,7 +24,7 @@
24
24
 
25
25
  <td class="px-6 py-4 whitespace-nowrap">
26
26
  <%= link_to [:account, membership], class: 'block flex items-center group hover:no-underline no-underline' do %>
27
- <div class="flex-shrink-0 h-10 w-10">
27
+ <div class="shrink-0 h-10 w-10">
28
28
  <%= image_tag membership_profile_photo_url(membership), title: membership.label_string, class: 'h-10 w-10 rounded-full' %>
29
29
  </div>
30
30
 
@@ -42,7 +42,7 @@
42
42
  >
43
43
 
44
44
  <% menu = capture do %>
45
- <div class="flex items-center flex-shrink-0 p-4 bg-blue-700 md:rounded-tl-lg">
45
+ <div class="flex items-center shrink-0 p-4 bg-blue-700 md:rounded-tl-lg">
46
46
  <%= image_tag image_path("logo/logo.png"), class: 'h-5 w-auto mx-auto' %>
47
47
 
48
48
  <div class="lg:hidden absolute right-0">
@@ -171,6 +171,12 @@
171
171
  <i class="fal fa-brackets-curly ti ti-view-list-alt"></i>
172
172
  <% end %>
173
173
  <% end %>
174
+
175
+ <%= render 'account/shared/menu/item', url: '/docs/contributing.md', label: 'Contributing' do |p| %>
176
+ <% p.content_for :icon do %>
177
+ <i class="fal fa-github-alt ti ti-github"></i>
178
+ <% end %>
179
+ <% end %>
174
180
  <% end %>
175
181
 
176
182
  <%= render 'account/shared/menu/section', title: 'Accounts & Teams' do %>
@@ -353,11 +359,11 @@
353
359
  >
354
360
  <%= menu %>
355
361
  </div>
356
- <div class="flex-shrink-0 w-14" aria-hidden="true"></div>
362
+ <div class="shrink-0 w-14" aria-hidden="true"></div>
357
363
  </div>
358
364
  </div>
359
365
 
360
- <div class="hidden lg:flex lg:flex-shrink-0 overflow-y-auto bg-gradient-to-b from-primary-700 to-primary-800 dark:from-base-800 dark:to-base-800">
366
+ <div class="hidden lg:flex lg:shrink-0 overflow-y-auto bg-gradient-to-b from-primary-700 to-primary-800 dark:from-base-800 dark:to-base-800">
361
367
  <div class="w-64">
362
368
  <%= menu %>
363
369
  </div>
@@ -0,0 +1,94 @@
1
+ # Contributing to Bullet Train
2
+
3
+ To contribute to Bullet Train there are two main repos that are involved:
4
+
5
+ * [The starter repo](https://github.com/bullet-train-co/bullet_train) - This is the repo that you clone to start a new Bullet Train app.
6
+ * [The `core` repo](https://github.com/bullet-train-co/bullet_train-core) - This is where all (OK, most) of the gems live.
7
+
8
+ ## Linking Ruby gems
9
+
10
+ When working on bug fixes or new features it can be useful to use a local copy of the `core` gems instead of the published versions.
11
+ You can do this in either the starter repo itself, or in a "downstream app" that has been created from the starter repo.
12
+
13
+ We have a convenience script in the starter repo at `bin/hack` which helps get things setup for you.
14
+
15
+ `bin/hack` supports two different models of organizing your filesystem for `core` development.
16
+
17
+ 1. The "nested repo approach" - If you run `bin/hack` with no arguments it will clone the `core` repo into your project at `local/bullet_train-core`.
18
+ It will also attempt to open that repo in your editor/IDE.
19
+ 2. The "peer repo approach" - If you already have the `core` repo cloned you can pass the `--link` option to `bin/hack` followed by a path to `core`.
20
+ For instance `bin/hack --link ../bullet_train-core`.
21
+
22
+ In either case `bin/hack` will modify the `Gemfile` in your project and change the lines for all of the `bullet_train*` gems to point to a local copy.
23
+
24
+ Lines that start like this:
25
+
26
+ ```ruby
27
+ gem "bullet_train", BULLET_TRAIN_VERSION
28
+ ```
29
+
30
+ Will become this:
31
+
32
+ ```ruby
33
+ gem "bullet_train", path: "../bullet_train-core/bullet_train"
34
+ ```
35
+
36
+ Once that's done you can start/restart your dev server and then chnages you make within your `core` repo will be reflected in your local app.
37
+
38
+ ## Linking Javascript packages
39
+
40
+ If you need to make changes to any of the Javascript packages from the `core` gems the process is a little bit different.
41
+
42
+ We use `yalc` to handle the details of making a local package available to your local app.
43
+
44
+ First you need to go into the directory for the gem/package that you're working with, then build the JS package, and make it available to local projects using `yalc push`.
45
+ (Don't worry, you're not pushing to anywhere other than your local dev environment.)
46
+
47
+ So, if you're working with the `bullet_train-fields` JS package you'd do this:
48
+
49
+ ```
50
+ cd bullet_train-core/bullet_train-fields
51
+ yarn build
52
+ yarn yalc push
53
+ ```
54
+
55
+ After pushing you should see a line in your terminal that looks something like this:
56
+
57
+ ```
58
+ @bullet-train/fields@1.32.0 published in store.
59
+ ```
60
+
61
+ Next you can link that package into your local app or starter repo. (You'll be bouncing between the gem directory and your app directory, so it's convenient to use two different terminal sessions for this.)
62
+ Go into your app or starter repo directory and then use `yalc link` to connect your local package.
63
+
64
+ ```
65
+ cd bullet_train
66
+ yarn yalc link @bullet-train/fields
67
+ ```
68
+
69
+ Now your local app will be running with the JS code from your local copy.
70
+
71
+ As you're making changes you can test them out in your local app by building and pushing the package again.
72
+
73
+ So, for this example, back in the `bullet_train-core/bullet_train-fields` directory you can run:
74
+
75
+ ```
76
+ yarn build; yarn yalc push
77
+ ```
78
+
79
+ Now in addition to seeing a line about the package being published to the store, you should also seem some lines about it being pushed into your local app.
80
+
81
+ ```
82
+ @bullet-train/fields@1.32.0 published in store.
83
+ Pushing @bullet-train/fields@1.32.0 in /Users/jgreen/projects/bullet-train-co/bullet_train
84
+ Package @bullet-train/fields@1.32.0 linked ==> /Users/jgreen/projects/bullet-train-co/bullet_train/node_modules/@bullet-train/fields
85
+ ```
86
+
87
+ Each time that you rebuild and re-push the package the file watcher in your project (or starter repo) should notice the change and rebuild your assets.
88
+
89
+ ## Managing cross-repo pull requests
90
+
91
+ Sometimes a particular change will require modifications to both the starter repo and the `core` repo. In these cases you should use the same branch
92
+ name in both repos. That will allow CI to hook them together and run tests in the right way.
93
+
94
+ Happy hacking!
data/docs/index.md CHANGED
@@ -24,6 +24,8 @@
24
24
  - [Test Suite](/docs/testing.md)
25
25
  - [Magic Test: Point-and-Click Test Writing](https://github.com/bullet-train-co/magic_test) <i class="ti ti-new-window ml-2"></i>
26
26
  - [Application Options](/docs/application-options.md)
27
+ - [Application Hash](/docs/application-hash.md)
28
+ - [Contributing to Bullet Train](/docs/contributing.md)
27
29
 
28
30
  ## Accounts & Teams
29
31
  - [Authentication](/docs/authentication.md)
@@ -1,3 +1,3 @@
1
1
  module BulletTrain
2
- VERSION = "1.33.0"
2
+ VERSION = "1.34.0"
3
3
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: bullet_train
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.33.0
4
+ version: 1.34.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Andrew Culver
@@ -597,6 +597,7 @@ files:
597
597
  - docs/authentication.md
598
598
  - docs/billing/stripe.md
599
599
  - docs/billing/usage.md
600
+ - docs/contributing.md
600
601
  - docs/desktop.md
601
602
  - docs/docker.md
602
603
  - docs/field-partials.md