Julius Kiekbusch

@decadence This kind of seems like a PHPStorm Problem, because it tries to search `class-string` within a namespace instead of using it as a literal. No clue why though.

Yeah it would. In this case the class was not tested yet and due to an update to an external component, the implementation didn't match anymore. Which would have resulted...

> Looking into it. As a side-note, this seems like something that should error our in tests regardless of whether or not you use architecture testing. Yeah, I would have...

Maybe something to look forward to: Make pint 40x faster (using parallel option): https://github.com/laravel/pint/pull/376 Hopefully this will be released soon.

Hey @duncanmcclean thanks for looking into it. I also stripped down the repository now and the issue still occurs. Strip Down Commit: https://github.com/Jubeki/statamic-bug-antlers-and-bard/commit/13241052935bf07a635889954d1f574590d9d9df I also have deploy the same repository,...

The problem lies within using `{{ contact:details }}` within another Bard Field (on the Homepage in this case) and not directly in a view.

I must say, I didn't really think about using a set for this, because I only thought about outputting the globals value like with antlers, and that was the simplest...

From a security and maintainability perspective, I also agree, that aligning with the RFC is better! But of course at the same time aligning with the RFC, also makes it...

I would also like it if there are test cases with the old columns, so that you can continue checking if everything works as expected.

I tried creating a PR for `aws/aws-sdk-php` regarding the implicit nullable type which adds a lot of deprecations in this Test Suite: - https://github.com/aws/aws-sdk-php/pull/2995 ~It was closed because it was...