GitHub user Jarvx200 edited a comment on the discussion: Avoiding redundancy in Info Builders
Hey there, my suggestion to this problem is instead of abstracting we might actually find using composition a bit more helpful for the common fields. The main benefit would be not needing to merge the abstraction tree of the builders and than having to use generics. (#764 rollback) We could create a simple **proxy class** that would contain those attributes and have them composited into the builders. Another suggestion would actually be to use an interface with default methods for each of the fields, the only problem here being as far as I can see that it would still require some sort of state to handle transitional data states. That could be done like a pipeline but I suspect we might end up in a similar situation. If you want, I can mock some code samples for each one of my proposal and continue discussing forward on the issue! @Thespica @yangxk1 GitHub link: https://github.com/apache/incubator-graphar/discussions/795#discussioncomment-14786813 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
