-
Notifications
You must be signed in to change notification settings - Fork 823
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stop using deprecated code in CMS 4 for core #10542
Labels
Comments
3 tasks
This was referenced Oct 12, 2022
This was referenced Nov 2, 2022
NON-FRAMEWORKAdmin - deprecated
Asset-admin - deprecated
Assets - deprecations added
Assets - migrations
Assets - deprecated
Behat-extension - deprecated
Campaign-admin - deprecated
CMS - deprecations added
CMS - deprecated
Config - deprecated
ErrorPage - deprecated
Event-dispatcher - deprecated
Frameworktest - deprecated
GraphQL - deprecated
Login froms - deprecated
Mimevalidator - deprecated
Registry - deprecated
Reports - deprecated
Serve - deprecated
Session manager - deprecated
Siteconfig - deprecated
Testsession - deprecated
Versioned - deprecations added
Versioned - undeprecated
Versioned - deprecated
Versioned admin - deprecated
FRAMEWORK"Use xyz instead" - Undeprecated
"Use xyz instead" - Migrations
"Use xyz instead" - Notes
Deprecated - "Use xyz instead"
Other Notes:
Things in "Will be removed without equivalent functionality" that will be removed in CMS5, though we cannot remove in CMS4
Undeprecated things in "Will be removed without equivalent functionality" because there is no upgrade path
Deprecated - "Will be removed without equivalent functionality"
Deprecated - other - notes
Deprecated - other - undeprecated
Deprecated - other
|
This was referenced Nov 3, 2022
There should probably be a docs PR as well - the 4.12 changelog should mention things that you've newly deprecated. |
@emteknetnz could you check this failed CI, please. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Splitting from #10500
Acceptance criteria
config()->update()
toconfig()->set()
if they are using non-arraysNotes
Ensure that we have a reliable way to surface deprecation warnings from up-stream dependencies such as symfony and guzzle e.g. investigate using this https://symfony.com/doc/current/components/phpunit_bridge.html#usageImplementation notes - stand-alone CI
Background for CI deprecation job
I tried turning on deprecation warning on a CMS 4 fork on emteknetnz/silverstripe-framework by simply changing the Deprecation::notification_version in _config.php from 4.0.0 to 5.0.0
While most deprecation warnings were harmless, a bunch of them causes the build to go red e.g.
Config_ForClass:update()
Because of it causing the build to go red, it's not viable to have a permanent job with deprecation warnings turned on. This is doubly so because gha-ci is an upstream provider for non cms-squad modules that use the CI.
I also don't think have a permanent deprecation job on is even really helpful. There is no further use for it once the work is this card and the corresponding card "Stop using deprecated code in CMS 4 for sink" is completed.
silverstripe/installer run including PRs below
PRs
Bonus PR to update silverstripe.log
The text was updated successfully, but these errors were encountered: