Making DbObject more idiomatic

[mikolak-net]

The DbObject helper trait has several "non-Scalastic" qualities:

• the underlying, mutable Vertex is exposed via getVertex (especially problematic since DbObject seems to be intended to be mixed into case classes),
• most of the utility methods are "expression unfriendly" (return Unit).

Obviously, there needs to be a way to interface with the "main" blueprints API, but is there a reason for this particular implementation?

I would be very happy to produce a PR with a more idiomatic approach, but I'd like to understand the rationale for the status quo first.

[anvie]

There is no specific reason for that implementation, you are welcome to provide a PR, I'll love to review :)

[mikolak-net]

Excellent, I'll get to it then.