ju1ius

@la10736 Hi, this is a great step forward ! 👍🏻 However this does not cover the case where there can be several test cases per file. For example, let's say...

Indeed, this is not working as of version 0.8.1: ```rust #[php_class] pub struct Greeter(String); #[php_impl] impl Greeter { pub fn __construct(who: String) -> Self { Self(who) } pub fn greet(&self)...

@joehoyle Yes that's the issue. The `create_object` handler should just forward the `zend_class_entry` pointer to [internal_new](https://github.com/davidcole1340/ext-php-rs/blob/dddc07f587cd5d40f3b3ff64b9a59fba8299d953/src/types/class_object.rs#L105) (the Zend engine guarantees that it points to either your registered class entry or...

Yeah, I tried to fix it sometime ago but ran into so much fundamental issues that I ended up writing my own library from scratch. 🤣

> @ju1ius ah I see! Any chance that code is open sourced? It is planned yes, but no clear ETA. Probably sometime after the PHP 8.3 release.

Hi, > Duplicate? #116 Indeed seems like a dupe, sorry for missing that. > The correct answer to fix the auto complete issue would be to have phpunit stubs installed...

After reading through #116, I still think adding a CLI flag to set the full path is the right thing to do. First because it's use case is not limited...

> I also do not understand why PHPStorm requires the extension. I don't know either. However I do remember having had issues when trying to `include` things using a phar...

> I do not believe your example of "jumping to the implementation" is actually a real requirement. You do not do that to PHP's code either, yet you use the...

> Additionally, using the hybrid phar, you get autocomplete for things you do not want nor need, independent of your acutal use case. When writing tests, you do not need...