sohyl87

private function parse_tweet($text){

    //links
    $text = preg_replace(
            '@(https?://([-\w\.]+)+(/([\w/_\.]*(\?\S+)?(#\S+)?)?)?)@',
             '<a href="$1">$1</a>',
            $text);

    //users
    $text = preg_replace(

craigbeck

  query IntrospectionQuery {
    __schema {
      queryType { name }
      mutationType { name }
      subscriptionType { name }
      types {
        ...FullType
      }
      directives {

tomaj

# Be carefull - find also optional extensions
find . -name "composer.json" -exec grep -H '"ext-' {} \; | awk -F '"' '{print $2}' | sort | uniq

ruudk

How to find the files that are the slowest to analyze with PHPStan?

For us, PHPStan became a bit slower with every release. We have a very large codebase with 10.000+ classes. There seem to be a few known issues related to big arrays.

See: phpstan/phpstan#8353 phpstan/phpstan#8146

To understand which files are problematic we run the following command: