-
Notifications
You must be signed in to change notification settings - Fork 25
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
Add teaser selection resolver #83
Add teaser selection resolver #83
Conversation
@wachterjohannes Is it enough, that the |
@luca-rath the teaser should be returned with the resolved media. |
@luca-rath as alex mentioned we should resolve the media and write into the reference store |
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.
The content resolver I think can be simplified a little bit.
$items = [ | ||
[ | ||
'id' => '74a36ca1-4805-48a0-b37d-3ffb3a6be9b1', | ||
'type' => 'pages', |
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.
its a little bit strange from outside that we return here pluralized
types and in the structure itself it are the singular
template key but will at current state create an issue for it. #84 /cc @nnatter
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.
Yes I totally agree
@alexander-schranz can you recheck and merge if all of your thoughts are implemented |
This
TeaserSelectionResolver
resolves teasers to something like