kotovalexarian-likes-github
/
rails--rails
mirror of https://github.com/rails/rails.git
1
0
Fork 0
Code Releases Activity

chore: fix grammar and spelling in Markdown and Ruby files

This commit is contained in:
John Bampton 2021-04-15 19:32:27 +10:00
parent 01fcf11f45
commit 7260f79d7a
5 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
guides/source/action_controller_overview.md
View File

@ -1078,7 +1078,7 @@ be able to send arbitrary data to the browser at specific points in time.
#### Incorporating Live Streaming
Including `ActionController::Live` inside of your controller class will provide
all actions inside of the controller the ability to stream data. You can mix in
all actions inside the controller the ability to stream data. You can mix in
the module like so:
```ruby
@ -1191,7 +1191,7 @@ Rescue
Most likely your application is going to contain bugs or otherwise throw an exception that needs to be handled. For example, if the user follows a link to a resource that no longer exists in the database, Active Record will throw the `ActiveRecord::RecordNotFound` exception.
Rails default exception handling displays a "500 Server Error" message for all exceptions. If the request was made locally, a nice traceback and some added information gets displayed, so you can figure out what went wrong and deal with it. If the request was remote Rails will just display a simple "500 Server Error" message to the user, or a "404 Not Found" if there was a routing error or a record could not be found. Sometimes you might want to customize how these errors are caught and how they're displayed to the user. There are several levels of exception handling available in a Rails application:
Rails default exception handling displays a "500 Server Error" message for all exceptions. If the request was made locally, a nice traceback and some added information gets displayed, so you can figure out what went wrong and deal with it. If the request was remote Rails will just display a simple "500 Server Error" message to the user, or a "404 Not Found" if there was a routing error, or a record could not be found. Sometimes you might want to customize how these errors are caught and how they're displayed to the user. There are several levels of exception handling available in a Rails application:
### The Default 500 and 404 Templates

4
guides/source/action_mailbox_basics.md
View File

@ -76,7 +76,7 @@ $ bin/rails action_mailbox:ingress:exim URL=https://example.com/rails/action_mai
### Mailgun
Give Action Mailbox your
Mailgun Signing key (which you can find under Settings -> Security & Users -> API security in Mailgun)
Mailgun Signing key (which you can find under Settings -> Security & Users -> API security in Mailgun),
so it can authenticate requests to the Mailgun ingress.
Use `bin/rails credentials:edit` to add your Signing key to your application's
@ -105,7 +105,7 @@ fully-qualified URL `https://example.com/rails/action_mailbox/mailgun/inbound_em
### Mandrill
Give Action Mailbox your Mandrill API key so it can authenticate requests to
Give Action Mailbox your Mandrill API key, so it can authenticate requests to
the Mandrill ingress.
Use `bin/rails credentials:edit` to add your API key to your application's

2
railties/test/application/configuration_test.rb
View File

@ -1843,7 +1843,7 @@ module ApplicationTests
app "development"
# TODO: Test deprecation message, assert_depcrecated { app "development" }
# TODO: Test deprecation message, assert_deprecated { app "development" }
# does not collect it.
assert_equal [X], C.descendants

12
railties/test/application/rake/multi_dbs_test.rb
View File

@ -714,7 +714,7 @@ module ApplicationTests
%>
adapter: sqlite3
animals:
database: db/develoment_animals.sqlite3
database: db/development_animals.sqlite3
adapter: sqlite3
YAML
@ -738,7 +738,7 @@ module ApplicationTests
<% end %>
adapter: sqlite3
animals:
database: db/develoment_animals.sqlite3
database: db/development_animals.sqlite3
adapter: sqlite3
YAML
@ -759,7 +759,7 @@ module ApplicationTests
database: <% if Rails.application.config.database %><%= Rails.application.config.database %><% else %>db/default.sqlite3<% end %>
adapter: sqlite3
animals:
database: db/develoment_animals.sqlite3
database: db/development_animals.sqlite3
adapter: sqlite3
YAML
@ -779,7 +779,7 @@ module ApplicationTests
<%= Rails.application.config.database ? 'database: db/development.sqlite3' : 'database: db/development.sqlite3' %>
adapter: sqlite3
animals:
database: db/develoment_animals.sqlite3
database: db/development_animals.sqlite3
adapter: sqlite3
YAML
@ -800,7 +800,7 @@ module ApplicationTests
custom_option: <%= ENV['CUSTOM_OPTION'] %>
adapter: sqlite3
animals:
database: db/develoment_animals.sqlite3
database: db/development_animals.sqlite3
adapter: sqlite3
YAML
@ -820,7 +820,7 @@ module ApplicationTests
database: db/default.sqlite3
adapter: sqlite3
animals:
database: db/develoment_animals.sqlite3
database: db/development_animals.sqlite3
adapter: sqlite3
migrations_paths: db/animals_migrate
YAML

2
railties/test/application/zeitwerk_integration_test.rb
View File

@ -156,7 +156,7 @@ class ZeitwerkIntegrationTest < ActiveSupport::TestCase
assert require_dependency("#{app_path}/app/models/user.rb")
end
test "require_dependency supports arguments that repond to to_path (#{add_aps_to_lp})" do
test "require_dependency supports arguments that respond to to_path (#{add_aps_to_lp})" do
add_to_config "config.add_autoload_paths_to_load_path = #{add_aps_to_lp}"
app_file "app/models/user.rb", "class User; end"
boot