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
I’m about to implement a get_adjacent_edge_versions method in the client. So far, we only have a method for retrieving adjacent lineage edges. Is it a good idea for me to implement this method, or is the fact that I need it a sign that I’m mis-using Ground? The way I see it, these methods would aid in implementing a Flor query engine for Ground.
The text was updated successfully, but these errors were encountered:
There's no reason we shouldn't have this method. It makes perfect sense to me. It was definitely in a previous version but was probably lost in one of the rewrites. If you need it, you should definitely go for it!
I’m about to implement a
get_adjacent_edge_versions
method in the client. So far, we only have a method for retrieving adjacent lineage edges. Is it a good idea for me to implement this method, or is the fact that I need it a sign that I’m mis-using Ground? The way I see it, these methods would aid in implementing a Flor query engine for Ground.The text was updated successfully, but these errors were encountered: