Conversation
MKodde
left a comment
There was a problem hiding this comment.
Nice work! We had a small discussion IRL where I questioned the current solution:
- Could you make a more 'generic' solution for the object and array types that you now added. This would need to include passing the type of the array items that are stored for additional type checking. And maybe passing a max length as some types have different requirements for that..
- Keep the current setup but add some additional (unit or integration) tests. I've found a couple of unit tests for two of the existing types
Question: are the types used in the existing functional tests? Or are they bypassed by the custom mock solution?
805c922 to
271256a
Compare
271256a to
cb43e68
Compare
cb43e68 to
fdc995d
Compare
fdc995d to
84b50bb
Compare
kayjoosten
left a comment
There was a problem hiding this comment.
Test are still failing
6f86ba5 to
074c48f
Compare
b019847 to
29b6168
Compare
|
17fbd2f to
dbadae3
Compare
- The old array / object serialization types from doctrine have been moved / integrated into our codebase for backward compatability. - Fix typo in allowed_idp_entity_ids. The db is a medium text, which is 16777215 bytes. This change aligns the column with the mapping. - Make the nullable: false explicit to avoid future confusion. Confusion could stem from the fact that the fields are nullable in code, but not nullable in the database. This is because a serialized `null` results in something like `s:` in the database.
dbadae3 to
b83392f
Compare
|
My earlier comparison was not correct. Doctrine does in fact want to remove the comments, and migrate longtext columns to json. In this PR, I reinstated the length limits so the correct column types are used matching prod. The nulls are also fixed. |
| #[Test] | ||
| public function an_object_round_trips_correctly(): void | ||
| { | ||
| $type = Type::getType(SerializedObjectType::NAME); |
Needed for SF 6.4