[ 
https://issues.apache.org/jira/browse/TINKERPOP-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stephen mallette updated TINKERPOP-1975:
----------------------------------------
    Labels: breaking  (was: )

I went down a long winding path introducing new bytecode infrastructure and 
serialization and reflection hacks and other awful things to get this working 
but then realized that I had much of what I needed for {{with()}} already 
present with {{Parameters}} which works perfectly as a holder for step 
configuration data. 

As a result of looking deeply at how {{Parameters}} worked I ended up making 
some adjustments and those changes ends up breaking APIs for a couple of 
reasons:

1. I moved {{Parameterizing}} interface to the package that held all the other 
marker interfaces. Not sure why it was where it was.
2. I created the new {{Configuring}} interface which introduced a 
{{configure()}} method which replaced (and thus removed) the 
{{Parameterizing.addPropertyMutations()}} method. I didn't bother to try to 
deprecate because it just didn't seem to make sense to keep that method around 
and it's an easy fix (just rename the method).

Anyway, this new approach is looking pretty nice as it fits our existing models 
for doing things really nicely.

> Introduce with() step modulator
> -------------------------------
>
>                 Key: TINKERPOP-1975
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1975
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.3.3
>            Reporter: stephen mallette
>            Assignee: stephen mallette
>            Priority: Major
>              Labels: breaking
>             Fix For: 3.4.0
>
>
> The {{with()}} step modulator provides a general way to provide 
> configurations to steps in much the same way {{withStrategies()}} or 
> {{withSideEffects()}} are used to configure traversals.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to