PHP 8.2 compatibility

Test passing on local hence requesting review.

All changes are looking fine to me wrt Drupal version 10.0.7 and below tested with PHP 8.1 and 8.2 ~~ Hence marking this as RTBC.

Note: One test case is failing against for Drupal version 10.1.x with php 8.2

Review posted. Try to avoid unrelated changes, the only really required change here that is in scope is defining the new properties.

One more comment.

Please review MR!47, FunctionalJavascriptTest is failing on Drupal 10.1 caused by bulk operation with default option as -select-
Attaching the screenshot for your reference.

Changes looks good to me , hence moving into RTBC

Assigning to myself as I'm triaging all RTBC issues.

Been reviewing the comments and the commits and diffing things. Having the coding standard changes in it MR does make it harder to review which is something @Berdir mentioned above.

All permutations of tests have been run and pass which is good. I'm just trying to decide if this should be manually tested on all these version but that would be a bit labor intensive. Also, the info file has ^9.2 so I'll fire up tests for that at least to see what happens.

Testing on 9.2 + PHP 8.0 went well.

I've tested w/ PHP 8.2 and Core 10.1. Without the patch, when I went to re-save all views, I got warnings about dynamic properties. With the patch, I no longer get those warnings.

Tested using drush php:

$entities = \Drupal::entityTypeManager()->getStorage('view')->loadMultiple();
foreach ($entities as $entity) {$entity->save();}

Thanks @heddn. If this can be tested on 9.2 with PHP 7.4 then I'd feel comfortable merging it.

Unassigning from me for now as I'm going to be on vacation for awhile and not sure when I could test this.

Does anything block the stable release with PHP 8.2 deprecation fixes?

Attaching patch to use in composer.json

Merged, thanks for your contributions.

Again, try to limit changes to what is actually required in an issue, that makes it far easier to review and get committed.

Automatically closed - issue fixed for 2 weeks with no activity.