@@ -954,7 +954,7 @@ to work on some subclass, things get interesting.
954
954
While working with ` Polygon ` you do not need to be aware of all its descendants,
955
955
because anything in the table is by definition a polygon, but when working with
956
956
subclasses Active Record needs to be able to enumerate the types it is looking
957
- for. Let’ s see an example.
957
+ for. Let' s see an example.
958
958
959
959
` Rectangle.all ` only loads rectangles by adding a type constraint to the query:
960
960
@@ -963,7 +963,7 @@ SELECT "polygons".* FROM "polygons"
963
963
WHERE " polygons" ." type" IN (" Rectangle" )
964
964
```
965
965
966
- Let’ s introduce now a subclass of ` Rectangle ` :
966
+ Let' s introduce now a subclass of ` Rectangle ` :
967
967
968
968
``` ruby
969
969
# app/models/square.rb
@@ -978,7 +978,7 @@ SELECT "polygons".* FROM "polygons"
978
978
WHERE " polygons" ." type" IN (" Rectangle" , " Square" )
979
979
```
980
980
981
- But there’ s a caveat here: How does Active Record know that the class ` Square `
981
+ But there' s a caveat here: How does Active Record know that the class ` Square `
982
982
exists at all?
983
983
984
984
Even if the file ` app/models/square.rb ` exists and defines the ` Square ` class,
@@ -1049,7 +1049,7 @@ end
1049
1049
1050
1050
The purpose of this setup would be that the application uses the class that
1051
1051
corresponds to the environment via ` AUTH_SERVICE ` . In development mode
1052
- ` MockedAuthService ` gets autoloaded when the initializer runs. Let’ s suppose
1052
+ ` MockedAuthService ` gets autoloaded when the initializer runs. Let' s suppose
1053
1053
we do some requests, change its implementation, and hit the application again.
1054
1054
To our surprise the changes are not reflected. Why?
1055
1055
0 commit comments