Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
minor #13811 [Form] Improve triggering of the setDefaultOptions depre…
…cation error (WouterJ) This PR was merged into the 2.7 branch. Discussion ---------- [Form] Improve triggering of the setDefaultOptions deprecation error Bundles wanting to support both Sf 2.3 and Sf 2.7 (which is a common requirement as both have at least 2 more years of maintaince) would have custom form types with both option methods defined (`setDefaultOptions` for <2.7 support and `configureOptions` for >2.7,>3.0 support). In such case, I don't think there is anything wrong with the code and a deprecation error shouldn't be triggered. | Q | A | ------------- | --- | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | - | License | MIT | Doc PR | - Commits ------- 811b711 Improve triggering of the deprecation error
- Loading branch information