inspired by graphql (define schema in declaretive way) however gql itself only walks from top to bottom, which lack the ability to change data after it's descd

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