You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NOTE: Not urgent or blocking! There are already currently working workarounds in SVCs side for this.
SVCs team has a function manualInitialize which is used mainly for: this._startChangesetIndex = this.synchronizationVersion.index + 1;.
We should support SVCs team desire to determine the startChangesetIndex so that they do not have to have a manualInitialize which has to set a private property _isSynchronization on the core transformer.
Potential Options
Provide a hook onTransformerInitialized which lets consumers run code right after the transformer is initialized and before it starts processing changes. Consumers would pass this function as part of the transformer options.
Adding method to transformer to get the startchangesetindex?
Maybe on red arrow could add?
Or somewhere in this function above
Concerns
I raised a concern on the below PR that I think could be relevant. #172
One other concern I have is, does the transformation services team ever setup the exporter manually before you call the transformer? Currently you'll need to add your custom changes before you call IModelTransformer.initialize(), which I personally ran into some trouble when trying to allow myself to do that in the tests (can look at timelinetestutil to see what changes I had to make to support that)
The text was updated successfully, but these errors were encountered:
PR linked will be to untangle initializing and calling processChanges, so consumers could run anything they wanted in between calling initialize() and process() on the transformer
Context
NOTE: Not urgent or blocking! There are already currently working workarounds in SVCs side for this.
SVCs team has a function
manualInitialize
which is used mainly for:this._startChangesetIndex = this.synchronizationVersion.index + 1;
.We should support SVCs team desire to determine the startChangesetIndex so that they do not have to have a
manualInitialize
which has to set a private property_isSynchronization
on the core transformer.Potential Options
onTransformerInitialized
which lets consumers run code right after the transformer is initialized and before it starts processing changes. Consumers would pass this function as part of the transformer options.Maybe on red arrow could add?
Or somewhere in this function above
Concerns
I raised a concern on the below PR that I think could be relevant.
#172
The text was updated successfully, but these errors were encountered: