mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
fix type fully qualified [ci skip]
This commit is contained in:
parent
18f342d82a
commit
56ac13e8e4
2 changed files with 4 additions and 4 deletions
|
@ -33,7 +33,7 @@ class RescueController < ActionController::Base
|
|||
class ResourceUnavailableToRescueAsString < StandardError
|
||||
end
|
||||
|
||||
# We use a fully-qualified name in some strings, and a relative constant
|
||||
# We use a fully qualified name in some strings, and a relative constant
|
||||
# name in some other to test correct handling of both cases.
|
||||
|
||||
rescue_from NotAuthorized, with: :deny_access
|
||||
|
|
|
@ -634,7 +634,7 @@ NOTE: Defined in `active_support/core_ext/module/introspection.rb`.
|
|||
|
||||
#### `parent_name`
|
||||
|
||||
The `parent_name` method on a nested named module returns the fully-qualified name of the module that contains its corresponding constant:
|
||||
The `parent_name` method on a nested named module returns the fully qualified name of the module that contains its corresponding constant:
|
||||
|
||||
```ruby
|
||||
module X
|
||||
|
@ -3708,9 +3708,9 @@ Extensions to `NameError`
|
|||
|
||||
Active Support adds `missing_name?` to `NameError`, which tests whether the exception was raised because of the name passed as argument.
|
||||
|
||||
The name may be given as a symbol or string. A symbol is tested against the bare constant name, a string is against the fully-qualified constant name.
|
||||
The name may be given as a symbol or string. A symbol is tested against the bare constant name, a string is against the fully qualified constant name.
|
||||
|
||||
TIP: A symbol can represent a fully-qualified constant name as in `:"ActiveRecord::Base"`, so the behavior for symbols is defined for convenience, not because it has to be that way technically.
|
||||
TIP: A symbol can represent a fully qualified constant name as in `:"ActiveRecord::Base"`, so the behavior for symbols is defined for convenience, not because it has to be that way technically.
|
||||
|
||||
For example, when an action of `ArticlesController` is called Rails tries optimistically to use `ArticlesHelper`. It is OK that the helper module does not exist, so if an exception for that constant name is raised it should be silenced. But it could be the case that `articles_helper.rb` raises a `NameError` due to an actual unknown constant. That should be reraised. The method `missing_name?` provides a way to distinguish both cases:
|
||||
|
||||
|
|
Loading…
Reference in a new issue