Experimenting with element/its type relationship #61
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The idea here:
ElementType
type is just a holder for the unique label and a factory for creatingTypedElement
sTypedElement
extends it. It holds theraw
value and add all those graph API methods.It comes from the idea that in the end we want just the
User
type for working with its values and theVertexType
valueuser
to refer to it asUser
s factory and the properties holder.In the end I'm not sure this idea work well. It does simplify some things, but doesn't improve the things much and you still need to write some boilerplate when defining
User
:self()
,fromRaw()
and the constructor.