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
All gRex.Gremlin scripts which are currently directly executed by gRex cannot be post-processed by Mogwai. This means that fetched graph Elements (typically Vertices) cannot be automatically - even optionally - instantiated as appropriate Mogwai Models, given their respective $type property (which is what Mogwai.client.query() currently does).
Possible solutions :
Add a new functionality to gRex
A typical solution would be to add a gRex.query() function with a single optional function parameter that would be responsible for post-processing all elements in the response.results array returned by Rexster. A default postProcess function could also be set at gRex instantiation in the settings object passed to gRex.connect().
Monkey patch gRex in Mogwai
Mogwai could override gRex.exec() and allow for optional post processing.
The text was updated successfully, but these errors were encountered:
All gRex.Gremlin scripts which are currently directly executed by gRex cannot be post-processed by Mogwai. This means that fetched graph Elements (typically Vertices) cannot be automatically - even optionally - instantiated as appropriate Mogwai Models, given their respective
$type
property (which is whatMogwai.client.query()
currently does).Possible solutions :
A typical solution would be to add a
gRex.query()
function with a single optionalfunction
parameter that would be responsible for post-processing all elements in theresponse.results
array returned by Rexster. A default postProcess function could also be set at gRex instantiation in thesettings
object passed togRex.connect()
.Mogwai could override gRex.exec() and allow for optional post processing.
The text was updated successfully, but these errors were encountered: