Thanks to visit codestin.com
Credit goes to github.com

Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: symfony/serializer
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v7.1.8
Choose a base ref
...
head repository: symfony/serializer
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v7.1.9
Choose a head ref
  • 3 commits
  • 2 files changed
  • 3 contributors

Commits on Nov 14, 2024

  1. prevent failures around not existing TypeInfo classes 

    Having a getType() method on an extractor is not enough. Such a method may
exist to be forward-compatible with the TypeInfo component. We still must
not call it if the TypeInfo component is not installed to prevent running into
errors for not-defined classes when the TypeInfo component is not installed.
    @xabbuh
    xabbuh committed Nov 14, 2024
    Configuration menu
    Copy the full SHA
    c210d2b View commit details
    Browse the repository at this point in the history

  2. [Serializer][PropertyInfo][Validator] TypeInfo 7.2 compatibility

    @mtarld
    mtarld committed Nov 14, 2024
    Configuration menu
    Copy the full SHA
    7afcfbb View commit details
    Browse the repository at this point in the history

  3. bug #58870 [Serializer][Validator] prevent failures around not existi… 

    …ng TypeInfo classes (xabbuh)

This PR was merged into the 7.1 branch.

Discussion
----------

[Serializer][Validator] prevent failures around not existing TypeInfo classes

| Q             | A
| ------------- | ---
| Branch?       | 7.1
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Issues        |
| License       | MIT

Having a `getType()` method on an extractor is not enough. Such a method may exist to be forward-compatible with the TypeInfo component. We still must not call it if the TypeInfo component is not installed to prevent running into errors for not-defined classes when the TypeInfo component is not installed.

Commits
-------

386453e prevent failures around not existing TypeInfo classes
    @nicolas-grekas
    nicolas-grekas committed Nov 14, 2024
    Configuration menu
    Copy the full SHA
    39ec8be View commit details
    Browse the repository at this point in the history
Loading