+1 - It is a good idea to separate them and have it consistent across older and
newer APIs.
-Bryan
> On Dec 1, 2017, at 2:39 PM, Alan Carroll
> wrote:
>
> As discussed in issue #2883, based on work in issue #2388, I would like to
> split the TXN and SSN plugin argument index reservations.
No. This would be a breaking API change for 8.0.
On Sun, Dec 3, 2017 at 3:44 PM, James Peach wrote:
>
>
> > On Dec 1, 2017, at 2:39 PM, Alan Carroll
> wrote:
> >
> > As discussed in issue #2883, based on work in issue #2388, I would like
> to split the TXN and SSN plugin argument index reservat
> On Dec 1, 2017, at 2:39 PM, Alan Carroll
> wrote:
>
> As discussed in issue #2883, based on work in issue #2388, I would like to
> split the TXN and SSN plugin argument index reservations. Currently nothing
> in the TS code base uses SSN plugin args therefore this change will not
> affect
> On Dec 1, 2017, at 3:39 PM, Alan Carroll
> wrote:
>
> As discussed in issue #2883, based on work in issue #2388, I would like to
> split the TXN and SSN plugin argument index reservations. Currently nothing
> in the TS code base uses SSN plugin args therefore this change will not
> affect
As discussed in issue #2883, based on work in issue #2388, I would like to
split the TXN and SSN plugin argument index reservations. Currently nothing
in the TS code base uses SSN plugin args therefore this change will not
affect any example, production, or experimental plugin provided by the code
