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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IBX-9379: Added Grace Period for archived versions #515
IBX-9379: Added Grace Period for archived versions #515
Changes from all commits
72aa20f
3acd147
48b0db3
337df43
9a166df
2f88274
d51676d
d41399c
f1f89fb
01f457b
7d895a2
b14af0f
13bcc0e
9966027
6efedc8
12feb97
8e5548b
6875253
7ebad66
d979a0a
0c35b84
9efaa4b
56fa8f1
7df510b
42b39cf
bec0cb4
32d3da4
811e55c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFAICS, this service is not shared, so won't that make it always new instance when injecting? Meaning are the items that you've collected in ContentService be available here in this instance?
Just asking, never used non-shared services in practice.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought this works in a little bit different, with making sure that it is not shared between requests in for example long living proceses, but I think you might be right (or we both are - and potential gains outweights problems) so I will remove shared config from service.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would be my expectation, but then maybe - given its generic name and namespace location - it should be a named service with some interface? Someone could be tempted to reuse this for different purpose.
Meaning defining it like:
so sb can create his own instance:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like
ibexa.cache_pool
is ofSymfony\Component\Cache\Adapter\TagAwareAdapterInterface
type, while you're expecting\Ibexa\Core\Persistence\Cache\Adapter\TransactionAwareAdapterInterface
in the constructor. Maybe we should decorate something?ibexa.cache_pool
can be theoretically replaced by different cache implementing/extendingTagAwareAdapterInterface
, so this might be important, if someone did so.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can just change type to
Symfony\Component\Cache\Adapter\TagAwareAdapterInterface
and see how that works, it should be fine due to method used.