Another dilemma I have maybe others can offer an opinion on. I have prisma with mongodb as the backend and I have for example a select input with 5000+ options that I already have in another mongodb collection. I'm debating making these options in the graphql schema so they can be "added" and such there but then that means a lot of querying I feel like to populate the fields, etc even with caching etc. Curious if anyone has any opinion on something like this. Main thing is wondering if it should really be a part of graphql if I think later on these morphs for example would be used as objects later in the system