Asmir Mustafic

I recommend to use `@ExclusionPolicy("ALL")`. In this way you can decide which props will be serialized (and skip all the eloquent magic)

The version exclusion strategy uses under the hood https://www.php.net/manual/en/function.version-compare.php Whatever is supported by `version_compare` should work here. It would be nice to move to https://github.com/composer/semver instead of `version_compare`

I'm not sure if I understand correctly, are you saying that you want `@SerializedName` only for serialization and not deserialization?

@andrei-dascalu i'm not sure that this is a valid bug report, did anyone manage to reproduce such issue?

@andrei-dascalu understood. ``` /** * @JMS/SerializedName("whatever") * / private string $testVar; ``` both serialization and deseralization should wotk/produce this json: `{ "whatever": "abc" } `

Thanks for the PR! Much appreciated! > This also checks that the accessor is not trying to access a property that does not exist on the object. See the getValue()...

`TypedArray` can be implemented without extending `Type` i think... but then you would need also `TypedHash`... few years ago I had in mind this: ```php class AccountListResponse { #[Type('array', [AccountSummary::class])]...

As said > few years ago I had in mind this: It was an idea, it has not been implemented

is adding this method signature a BC break? how would it behave if someone tries to override it ?

are you referring to something as https://github.com/schmittjoh/serializer/issues/424 ?