Pydantic-resolve, a hierarchical solution for data fetching and processing

I’ve used Pydantic with FastAPI, but can’t really get a solid feel for what this is doing. Can someone explain this to me like I’m 5?

A powerful tool to build nested view data.<p>based on pydantic, pydantic-resolve uses declaretive way to define and resolve (fetch) data from top to bottom<p>and provides post-process hooks from bottom to top (friendly for aggregation &amp; calculation)<p>it also provides visibility control over all fields.<p>concept diagram: <a href="https:&#x2F;&#x2F;raw.githubusercontent.com&#x2F;allmonday&#x2F;pydantic-resolve&#x2F;master&#x2F;doc&#x2F;imgs&#x2F;concept.png" rel="nofollow">https:&#x2F;&#x2F;raw.githubusercontent.com&#x2F;allmonday&#x2F;pydantic-resolve...</a>

inspired by graphql (define schema in declaretive way)<p>however gql itself only walks from top to bottom, which lack the ability to change data after it&#x27;s descdenants are resolved.<p>pydantic-resolve is progressive, this means you don&#x27;t need to introduce a big framework to build a nested view data, all you need to do is just:<p>- simpilify your query of root data (no complex sql any more, then you can reuse it)<p>- define the related data you wanted, and then let resolver to fetch it.<p>that&#x27;s all~

Could this be used to efficiently model an hierichical comment thread for example, like HN or reddit?

Is this more-or-less functional reactive programming (FRP) using Pydantic?