Matt Kane
Matt Kane
Generally the rule is most specific wins. The other option is to use arrays rather than objects, so the ordering is explicit
I think the clearest would be to use the same precedence rules as our routing
Yeah, I think keeping it explicit is best
Yes, I think that makes sense. I would also like to expose them to integrations, so you could in theory create an integration that abstracts that for your users
Continue the conversation in the stage 3 RFC https://github.com/withastro/roadmap/pull/1245
> Is this enacted somewhere yet/available as an experimental feature or on a beta version? No, still at the planning stage right now. We'll share experimental builds once they're available.
> Love the initial look of this. > > Will is still be possible to include a (zod) schema of some kind in the `defineCollection` function so if you are...
@reasonadmin I think support for implementing custom renderers is a must, and it would then make sense to allow these to be more flexible than a single `render()` function. Perhaps...
We have a preview release available, so I'd love if you can give it a try and share your feedback. Full details are in the PR, including changes in the...
I think that a lot of what @jlengstorf and @julrich are suggesting in terms of projections and resolvers could be achieved with the zod schema, particularly with things like `coerce`...