Make deprecation warning about enable_lazy_ghost_objects more explicit
#1731
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ostrolucky
approved these changes
Nov 23, 2023
dmaicher
approved these changes
Nov 23, 2023
|
Thanks @evertharmeling 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To ease fixing the deprecation related to
enable_lazy_ghost_objectsconfiguration, it would be helpful if the message was a bit more explicit.Currently the deprecation is shown as
Which makes you need to look up the line 569 and scroll back to the function name to know it is part of the
ormconfig.Adjusted message