Skip to content

Commit

Permalink
Merge pull request #559 from creative-commoners/pulls/5/deprecate-gra…
Browse files Browse the repository at this point in the history
…phql

DOC Deprecate CMS GraphQL endpoints
  • Loading branch information
GuySartorelli authored Aug 19, 2024
2 parents 5b809f8 + e592d10 commit eb8edb9
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions en/08_Changelogs/5.3.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -163,6 +163,7 @@ From 6.0 onwards, tokens will never be regenerated during session renewal, and t
- The [`RememberLoginHash::renew()`](api:SilverStripe\Security\RememberLoginHash::renew()) method has been deprecated without replacement, since the associated behaviour will be removed in 6.0.
- The `onAfterRenewToken` extension point within this method will likely be replaced with a new extension point in 6.0.
- The [`RememberLoginHash.replace_token_during_session_renewal`](api:SilverStripe\Security\RememberLoginHash->replace_token_during_session_renewal) configuration property has been added to allow disabling token regeneration during session renewal. This property will be removed in 6.0.
- Code for the CMS GraphQL `admin` schema which provided endpoints for the CMS has been deprecated and will be removed in CMS 6. Functionality which the GraphQL endpoints are currently responsible for will be replaced with regular Silverstripe controller endpoints instead. Extension hooks will be added to the new controller endpoints that return data to allow for customisation. Frontend schemas, such the `default` schema, will continue to work in CMS 6.

## Bug fixes

Expand Down

0 comments on commit eb8edb9

Please sign in to comment.