You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 3, 2018. It is now read-only.
Should the ProductListViewFactory be a final class? Now it is very hard to change the creation of e.g. a variantView.
I want to pass the options from VariantDocument:getOptions() to the VariantView via the ProductListViewFactory. But because this class is final, and the getVarantViews method is private I have to duplicate the whole class.
The text was updated successfully, but these errors were encountered:
It is meant to be final, even though we should extract more view factories, like ProductViewFactory, ProductVariantViewFactory, so that the interfaces would be more segregated and most of the extensions can be done by composition (just like with the document factories).
@11mb, Not sure if this can help you, but if you use symfony's service decoration you can inject the ProductListViewFactory into your new service, then simply call the createFromSearchResponse() on the inner service and perform your extra logic on the ProductListView object that is returned.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Should the ProductListViewFactory be a final class? Now it is very hard to change the creation of e.g. a variantView.
I want to pass the options from
VariantDocument:getOptions()
to theVariantView
via theProductListViewFactory
. But because this class is final, and thegetVarantViews
method is private I have to duplicate the whole class.The text was updated successfully, but these errors were encountered: