Suggestion to be able to expand relational fields

[cf-david-easton]

Hey there! I've found this loader super useful to get stuck into pocketbase with astro and one handy use case would be to be able to expand properties on a collection and have that reflected in its schema.

I've cloned the repo and investigated this myself and after trial and error have the tests running and have the expanded property working great in the load-entries.e2e-spec.ts.

I am about to look into building the schema generation but before I continue I wanted to make sure that you have the capacity and interest in receiving and reviewing a PR to add this feature.

Thanks so much for your work on this!

[pawcoding]

Hey there!

You are actually not the first one to request to use the expand parameter in this loader. I thought about adding this a while ago, but decided it's not worth it regarding the tradeoffs we'd need to make (see #33 (comment)). Seems like more people want this feature though and it would make the loader more flexible. But if we introduce this we need to carefully lay out the pros and cons of each approach somewhere in the documentation.

So if you (after reading my concerns with this) decide it's still worth it and you already have a proof-of-concept working, I'd be happy to take a look at it.

[cf-david-easton]

Thanks so much for linking the comment I didn't think to check the closed issues for anyone who was explored it before!

You make very good points that including expand as an option might cause people to use it as a shortcut that ends up having a negative impact.

As for what was mentioned regarding the unknown type, what I have done to resolve this issue is to ascertain the original collection of a expanded field and recursively call the generateSchema function to get that collection. I am only allowing 1 level of expanding here to avoid too much nesting.

I will finish off my last bit of the schema gen tests and make a PR and we can go from there if we think its worth the trade off. My use case in my astro project is just so I can break up a bigger entity collection that is only like 15 entries max into smaller re-usable bits but just so I can stitch them back together using expand rather than doing it separately in the app.