Christophe Coevoet

Strategy for dealing with invalid data

10

Currently, the way invalid data is handled in value objects and results is quite messy: - getters are typed with the expected type of the value - when creating the...

The CodeGenerator cache does not handle changes for patches properly

1

Changing `patches` in the manifest does not invalidate the cache of the code generator, while the cache contains the patched files, not the raw downloaded files. This makes it painful...

Closes #67

The readme says that installing this package is done as `@componentdriven/csf`. But the 0.1.0 release was done for `@storybook/csf`

Results for PHP 7

1

PHP 7 changed the JSON parser it uses, compared to PHP 5. So it would be great to update the result table to include results for PHP 7 as well.

Support Behat 3.0

6

Supporting Behat 3.0 involves a few changes: - the ContextInterface has been renamed to Context, which is probably why the special icon is not used on the file - steps...

Plugin is incompatible with PhpStorm 7

5

when opening a project after installing the plugin, an error message appears telling `createProject() returns null` when loading the Behat plugin. PhpStorm 7 EAP 131.98

Incompatible usages of callable param- tags should be reported as errors

1

### Feature request A callable parameter cannot be both later-invoked and immediately-invoked (the right way to represent a case where it can be used in both ways is to omit...

### Feature request To detect mistakes (typos in argument names for instance), those tags should have rules reporting invalid argument names, as done for `@param`. In https://phpstan.org/r/59daa22c-387c-4fd4-a671-6d8762f489b1, I would expect...

### Feature request https://phpstan.org/r/da19090a-2963-481b-8a46-f472a9eba4bd should report an error about `NonExistent` being an invalid this type for the closure as it does not exist. This should be similar to the way...