with sub-tasks to
cover what we agreed and moved your two tasks to sub-tasks of this issue.
I think both your PRs can be merged now, with
covering a clearer message
around the deprecation. I can handle that, but need to discuss with the
team around how we go about this first.
Not sure when we can make this switch, will discuss it with the team on
Friday and let you know.
On Fri, 27 Sep 2019 at 13:58, Jon Koops <jonkoops(a)gmail.com> wrote:
Great! I completely agree that the points outlined are the way
Let's focus on getting the deprecation message into the next release
together with the updated documentation. There are pull requests for these
changes and I would greatly appreciate a review of them.
I'll also modify the existing pull requests to incorporate the idea of a
'legacy' promise type and refer to it the documentation with some
elaboration that in a future version of Keycloak the default will change to
'native' over 'legacy'.
As for the timeline of the changing of the default to 'native' and
eventual removal of 'legacy' what would be the preferred moment to make