I’m Syed Ahmed Mubasirudin, a student at Osmania University. Over the past few weeks I’ve been exploring the Plone ecosystem, mainly focusing on how the REST API layer supports frontend behavior.
Recently, I’ve been working on a PR for plone.restapi(Add optional sort_on parameter to @vocabularies by hasansyed107 · Pull Request #1990 · plone/plone.restapi · GitHub) where I added an optional sort_on parameter to the @vocabularies endpoint. It gave me a good opportunity to understand batching, serialization consistency, and how documentation tests are structured. I appreciated the detailed review feedback from @davisagli and @stevepiercy — it helped me better understand expectations around tests and API changes.
I’m particularly interested in the “Support to manage content-type constraints in Volto” project. Since I’ve been working on the REST side recently, I started looking into how folder-level constraints are currently handled via ISelectableConstrainTypes and how that information might be exposed more effectively to Volto.
From a REST design perspective, I’m trying to understand whether it would make more sense to expose constraint data as part of folder GET responses (to avoid additional round-trips), or if a dedicated service would be cleaner from an architectural standpoint.
I’d appreciate any guidance on the preferred direction or considerations I should keep in mind as I explore this further.
Thanks!