Github Improve `strict_loading` violation error message by eileencodes · Pull Re...
source link: https://github.com/rails/rails/pull/41114
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Member
eileencodes commented on Jan 14
If you're using strict_loading in an application the previous message
only told you what class was lazily loaded. This change updates the
error message to include both the class and the association name. This
is useful because now you won't need to lookup the association name in
the application, the error message will tell you exactly which symbol
preload is missing.
Recommend
-
18
Hi, Wojtek from this side with a summary of the latest changes that will be available in the upcoming Rails 6.1. Ra...
-
23
Ignore strict loading violations on instances loaded through fixtures #40792
-
9
Contributor Author ayrton commented
-
4
New issue Strict loading cascade down to middle records #42494
-
11
Copy link Member eileencodes commented
-
6
New issue Improve error message for incorrect field accesses through raw pointers #91364
-
11
Copy link Contributor FabianWolff
-
12
Improve error message for E0081 #97456 ...
-
8
Syntax error or access violation: 1055 'posts.views' isn't in GROUP BY 1340 views 5 months ago Laravel While workin...
-
2
Conversation Member...
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK