CS-Birb commented on PR #909:
URL: 
https://github.com/apache/directory-scimple/pull/909#issuecomment-3290076754

   I'd struggled to think of an ideal fallback strategy with my previous PR 
too. Bit of a catch-22.
   
   Making the new method `default` has the lowest impact for existing 
implementations of the Repository, but to use the new method will require 
keeping an override for the old.
   
   Between M1 and the next production release there are already breaking 
changes in the Repository method signatures (I.e. version string to ETags, 
attribute references in more methods) so this may be a viable time to implement 
this as a breaking change.
   Adding new fields later on to the ScimRequestContext could then only be 
minor changes


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org

Reply via email to