Replace Model::persistence property with getter/setter#948
Merged
Conversation
a2ca9fb to
d263710
Compare
d263710 to
3bdbd6c
Compare
3bdbd6c to
4c65e89
Compare
4c65e89 to
1d415f8
Compare
af17abf to
6bf16d4
Compare
6bf16d4 to
34202ef
Compare
fd828eb to
5727b8d
Compare
5727b8d to
77d50e8
Compare
This was referenced Jun 29, 2022
DarkSide666
reviewed
Jun 30, 2022
Member
DarkSide666
left a comment
There was a problem hiding this comment.
Looks good. Have to fix tests.
Member
Author
|
what tests you mean? |
This file contains hidden or 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
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.
previously
Persistence::add()was not called whenModel::persistencewas set and it implied noPersistence::HOOK_AFTER_ADDhook was calledthis PR fixes it by replacing
Model::persistenceproperty with persistence getter/setterwith the newly introduced persitence
Model::setPersistence()setter,Persistence:add()call does not make any logical sense ( persistence can be set only once and never unset) and thus directPersistence:add()call newly throws an exceptionHere are several examples how to upgrade your code when setting persistence:
regex to locate old usage:
(?<!\w)(db|persistence)(?!\w).*->add\(When accessing the persistence,
Model::getPersistence()getter must be used and it throws when persistence is not set. To check if persistence is set, useModel::issetPersistence()method.regex to locate old usage:
->persistence(?!\w)