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
There was discussion in #106 about enabling better support for custom connections and recent changes were made to make that easier to implement in #107, #108, and #109.
Ideally it would be nice to have an easy way to declare connections with custom fields and edges with custom fields. I'm not exactly sure the best way to implement this, but it would be nice to have the customization and at the same time utilize the existing connection code, including slicing, etc.
@NeedleInAJayStack I know you mentioned you had begun to think about how this might be accomplished.
In addition, maybe it makes sense to also think about the "connection of a protocol" issue where because Node needs to implement Encodable, it is currently not possible to have a connection of a Union or Interface. There is a fix, and that is to create a wrapper type, but that's obviously not the cleanest approach.
A possible solution to 2 was mentioned here: #50 (comment)
The text was updated successfully, but these errors were encountered:
There was discussion in #106 about enabling better support for custom connections and recent changes were made to make that easier to implement in #107, #108, and #109.
@NeedleInAJayStack I know you mentioned you had begun to think about how this might be accomplished.
Node
needs to implementEncodable
, it is currently not possible to have a connection of aUnion
orInterface
. There is a fix, and that is to create a wrapper type, but that's obviously not the cleanest approach.A possible solution to 2 was mentioned here:
#50 (comment)
The text was updated successfully, but these errors were encountered: