@spree/docs 0.1.63 → 0.1.65
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.
- package/dist/developer/multi-tenant/configuration.md +1 -1
- package/dist/developer/tutorial/testing.md +4 -1
- package/dist/developer/upgrades/3.7-to-4.0.md +1 -1
- package/dist/developer/upgrades/4.0-to-4.1.md +1 -1
- package/dist/developer/upgrades/4.1-to-4.2.md +1 -1
- package/dist/developer/upgrades/4.2-to-4.3.md +1 -1
- package/dist/developer/upgrades/4.4-to-4.5.md +1 -1
- package/package.json +1 -1
|
@@ -36,6 +36,6 @@ SpreeMultiTenant::Config[:mail_from_name] = ENV.fetch('MAIL_FROM_NAME', 'Your Sa
|
|
|
36
36
|
SpreeMultiTenant::Config[:mail_from_address] = ENV.fetch('MAIL_FROM_ADDRESS', "support@#{Spree.root_domain}")
|
|
37
37
|
```
|
|
38
38
|
|
|
39
|
-
> **INFO:** `mail_from_name` is only used in admin emails, such as admin staff invitations, exports, etc. For consumer facing emails, this will be your tenant store name, eg.
|
|
39
|
+
> **INFO:** `mail_from_name` is only used in admin emails, such as admin staff invitations, exports, etc. For consumer facing emails, this will be your tenant store name, eg. `My Flower Store` (or whatever they set in the store settings).
|
|
40
40
|
>
|
|
41
41
|
> Also, customer facing emails will use the tenant email address in `Reply-To` header.
|
|
@@ -1,4 +1,7 @@
|
|
|
1
|
-
|
|
1
|
+
---
|
|
2
|
+
title: Testing
|
|
3
|
+
description: Learn how to write automated tests for the Brands feature
|
|
4
|
+
---
|
|
2
5
|
|
|
3
6
|
Automated testing is a crucial part of the development process. It helps you ensure that your code works as expected and catches bugs early.
|
|
4
7
|
Spree uses [RSpec](https://rspec.info), [Factory Bot](https://github.com/thoughtbot/factory_bot_rails), and [Capybara](https://github.com/teamcapybara/capybara) for testing.
|
|
@@ -5,7 +5,7 @@ order: 2
|
|
|
5
5
|
description: This guide covers upgrading a 3.7 Spree application to Spree 4.0.
|
|
6
6
|
---
|
|
7
7
|
|
|
8
|
-
> **NOTE:** If you're on an older version than 3.7 please follow previous upgrade guides and perform those upgrades incrementally
|
|
8
|
+
> **NOTE:** If you're on an older version than 3.7 please follow previous upgrade guides and perform those upgrades incrementally, eg.
|
|
9
9
|
>
|
|
10
10
|
> 1. [upgrade 3.4 to 3.5](3.4-to-3.5)
|
|
11
11
|
> 2. [upgrade 3.5 to 3.6](3.5-to-3.6)
|
|
@@ -5,7 +5,7 @@ order: 1
|
|
|
5
5
|
description: This guide covers upgrading a 4.0 Spree application to Spree 4.1.
|
|
6
6
|
---
|
|
7
7
|
|
|
8
|
-
> **NOTE:** If you're on an older version than 4.0 please follow previous upgrade guides and perform those upgrades incrementally
|
|
8
|
+
> **NOTE:** If you're on an older version than 4.0 please follow previous upgrade guides and perform those upgrades incrementally, eg.
|
|
9
9
|
>
|
|
10
10
|
> 1. [upgrade 3.5 to 3.6](3.5-to-3.6)
|
|
11
11
|
> 2. [upgrade 3.6 to 3.7](3.6-to-3.7)
|
|
@@ -5,7 +5,7 @@ order: 0
|
|
|
5
5
|
description: This guide covers upgrading a 4.1 Spree application to Spree 4.2.
|
|
6
6
|
---
|
|
7
7
|
|
|
8
|
-
> **NOTE:** If you're on an older version than 4.1 please follow previous upgrade guides and perform those upgrades incrementally
|
|
8
|
+
> **NOTE:** If you're on an older version than 4.1 please follow previous upgrade guides and perform those upgrades incrementally, eg.
|
|
9
9
|
>
|
|
10
10
|
> 1. [upgrade 3.7 to 4.0](3.7-to-4.0)
|
|
11
11
|
> 2. [upgrade 4.0 to 4.1](4.0-to-4.1)
|
|
@@ -6,7 +6,7 @@ hidden: true
|
|
|
6
6
|
description: This guide covers upgrading a 4.2 Spree application to Spree 4.3.
|
|
7
7
|
---
|
|
8
8
|
|
|
9
|
-
> **NOTE:** If you're on an older version than 4.1 please follow previous upgrade guides and perform those upgrades incrementally
|
|
9
|
+
> **NOTE:** If you're on an older version than 4.1 please follow previous upgrade guides and perform those upgrades incrementally, eg.
|
|
10
10
|
>
|
|
11
11
|
> 1. [upgrade 3.7 to 4.0](3.7-to-4.0)
|
|
12
12
|
> 2. [upgrade 4.0 to 4.1](4.0-to-4.1)
|
|
@@ -43,7 +43,7 @@ uninitialized constant Spree::Preference (NameError)
|
|
|
43
43
|
|
|
44
44
|
#### Update other initializers
|
|
45
45
|
|
|
46
|
-
Just like with `Spree::Config`, you may need to [update other
|
|
46
|
+
Just like with `Spree::Config`, you may need to [update other initializers in your application, that use autoloadable constants](https://rubyonrails.org/2021/9/3/autoloading-in-rails-7-get-ready).
|
|
47
47
|
|
|
48
48
|
For example, if you use `spree_auth_devise`, you'll need to update `config/initializers/devise.rb` and wrap the configuration in `Rails.application.config.after_initialize` block:
|
|
49
49
|
|