You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tinkerpop.apache.org by GitBox <gi...@apache.org> on 2020/08/20 14:59:36 UTC

[GitHub] [tinkerpop] spmallette commented on a change in pull request #1312: Make TinkerVertex non-final

spmallette commented on a change in pull request #1312:
URL: https://github.com/apache/tinkerpop/pull/1312#discussion_r474049523



##########
File path: gremlin-core/src/main/java/org/apache/tinkerpop/gremlin/process/traversal/step/map/GroupCountStep.java
##########
@@ -41,7 +41,7 @@
 /**
  * @author Marko A. Rodriguez (http://markorodriguez.com)
  */
-public final class GroupCountStep<S, E> extends ReducingBarrierStep<S, Map<E, Long>> implements TraversalParent, ByModulating {
+public class GroupCountStep<S, E> extends ReducingBarrierStep<S, Map<E, Long>> implements TraversalParent, ByModulating {

Review comment:
       We had originally made many of the steps `final` in the early days of TinkerPop 3.x to prevent extension by providers as they were changing frequently and we wanted to be able to introduce changes without worrying about breaking APIs. I'd imagine that most of the steps have largely stabilized at this point so perhaps that worry is no longer as much of a concern.  However, I still feel like these core step classes are TinkerPop's implementations and I'd not want to see our development blocked for fear of a breaking API change that affects providers (a behavioral change is different as it affects users and we would obviously be sensitive to that). 
   
   Perhaps it would be good to start a DISCUSS thread on this on the dev list to see if there is any concerns with removing `final` for all steps with the idea that breaking API changes become a possibility for providers on patch releases if they choose to directly extend these core step classes. wdyt?




----------------------------------------------------------------
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.

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