Malte Janz

See https://github.com/shopware/shopware/issues/3103#issuecomment-2574907192 We want to hear more about "why" this change is needed and what problem it solves. > 1. Why is this change necessary? > To show a preview...

Comment from design: - We shouldn't display cards inside other cards. It's fine to indent the content a little - Plaintext comes first on the detail page, but is second...

Fyi: closed this for now because of missing activity. Feel free to reopen and do the requested changes

Note: we have to investigate further when documents show up in the storefront. The docs say this about the option https://docs.shopware.com/en/shopware-6-en/settings/documents#:~:text=Show%20document%20in%20%22My%20Account%22%20area%20(14)%3A Specifically: > However, this does not apply retroactively to...

Note to self: Might be a good idea to scrape all twig component examples from the official documentation and check them against ludtwig for parsing errors. Same could be done...

Regarding my last comment, I created a concrete issue to experiment with that idea here: https://github.com/MalteJanz/ludtwig/issues/142

Please add a short PR description 🙂 . E.g. questions I would like to see answered in it: - What type of checks are being removed, e.g. checks for entity...

TBD if the latter should be supported by ludtwig, as it isn't part of the official twig documentation. But the error message at least should be improved to expect an...

@patzick It might make sense to have a clearly defined `enum` with all possible product types if you developing against a specific shopware installation. So it might make sense for...

@vienthuong > I still didn't get it why it's any different than store-api schema? if a 3rd add a new product type other than default ones, your store-api client might...