Simon Praetorius
Simon Praetorius
I'm currently experiencing the same problem. From my point of view, a solution could be to set the locale to `$TYPO3_CONF_VARS['SYS']['systemLocale']` before calling `pathinfo()` and to reset it afterwards. In...
I left a comment in the other issue: >Hi everyone, and thank you for bringing this to our attention. That's probably a tough one to fix, but we should at...
Another possibility just for the "in list" case could be to add literal and union types, like TypeScript has: https://www.typescriptlang.org/docs/handbook/2/everyday-types.html#literal-types But I'm not sure if it's worth the trouble implementing...
More like: ```xml ```
Yes, we use a similar approach (or rather workaround) in our projects. We are still working on a separate extension that will cover the whole responsive images subject (as well...
Ok, you can have a look here: https://github.com/sitegeist/media-components
Hi everyone, and thank you for bringing this to our attention. That's probably a tough one to fix, but we should at least look into it if it's solvable by...
> Since we also use the styleguide, it still won't work or? That could be a problem, yes. I actually haven't tried this myself... Usually, our components look and behave...
Good idea! This could be based on #144 which introduces a data structure for component metadata.
@AlexanderT8 In this case, you can probably wrap your inline script in a CDATA section. I would also say that you should extract longer scripts to a separate file and...