Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Representing nested fields #17

Open
TwiceII opened this issue Sep 30, 2019 · 0 comments
Open

Representing nested fields #17

TwiceII opened this issue Sep 30, 2019 · 0 comments

Comments

@TwiceII
Copy link

TwiceII commented Sep 30, 2019

Hey! First of all, I want to thank you for this awesome library, I have been using it lately and find it really useful.
One thing I wonder about is - how should one declare fields that are nested? I can represent them as separate entities, but sometimes they are not really worth it.
Suppose that I want to declare a schema for some Event in Event Sourcing style app. The Event entity has fields like id, type, timestamp which are flat fields, but also a payload which is nested and has its own fields. Making separate Payload entity is kinda awkward because:

  1. Semantically payload is just a part of Event entity.
  2. I don't want all the downstream Hodur plugins to treat it as "real" entity and create tables etc for them.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant