fix: Use property for TypedResponse.data to improve mypy type inference

- Convert data attribute to property with explicit T return type
- This should help mypy better understand the generic type relationship
- Bump version to 0.1.17
- Properties provide clearer type information than direct attributes

Author: codebydivine

pyproject.toml

@@ -26,7 +26,7 @@ classifiers = [
 ]
 keywords = ["blockchain", "ethereum", "solana", "defi", "nft", "api", "thegraph", "web3", "crypto"]
 dependencies = [
-    "divine-requests==0.1.15",
+    "divine-requests==0.1.16",
     "divine-type-enforcer==0.1.8",
     "anyio>=4.0.0",
 ]

src/thegraph_token_api/base.py

@@ -80,7 +80,6 @@ async def get_version(self) -> VersionResponse:
         response = await self.manager.get(
             f"{self.base_url}/version", headers=self._headers, expected_type=VersionResponse
         )
-        # Type assertion to help mypy understand divine-requests TypedResponse
         return response.data  # type: ignore[no-any-return]
 
     async def get_networks(self) -> NetworksResponse:
@@ -93,5 +92,4 @@ async def get_networks(self) -> NetworksResponse:
         response = await self.manager.get(
             f"{self.base_url}/networks", headers=self._headers, expected_type=NetworksResponse
         )
-        # Type assertion to help mypy understand divine-requests TypedResponse
         return response.data  # type: ignore[no-any-return]

src/thegraph_token_api/evm.py

@@ -313,7 +313,6 @@ async def get_balances(
             params=params,
             expected_type=BalancesResponse,
         )
-        # Return the full response object
         return response.data  # type: ignore[no-any-return]
 
     # ===== Transfer Methods =====