feat(graphql): integrate proto pagination system

[devin-ai-integration]

feat(graphql): integrate proto pagination system

Summary

This PR integrates the existing proto pagination infrastructure with the GraphQL layer, replacing manual SQL query building with the storage layer's pagination methods. The changes maintain backward compatibility with the existing GraphQL connection API while leveraging the proto Query struct and Page<T> results internally.

Key Changes:

• Added torii-proto dependency to GraphQL crate
• Created pagination.rs module with utility functions to convert between GraphQL connection arguments and proto pagination structures
• Updated GraphQL schema to accept Storage instance in context alongside Pool<Sqlite>
• Created specialized entity resolver using storage.entities() method with proto Query struct
• Maintained existing GraphQL connection API (first/last/after/before parameters)

⚠️ Important: This PR could not be built locally due to network authentication issues with git submodules, so compilation verification is needed.

Review & Testing Checklist for Human

• Verify compilation - The code builds successfully without errors (highest priority)
• Test entity GraphQL queries - Ensure entity queries with pagination parameters work correctly
• Verify type conversions - Check that proto Entity to GraphQL Entity conversions are correct
• Test pagination edge cases - Verify cursor-based pagination works with first/last/after/before parameters
• Check GraphQL schema consistency - Ensure the Storage context is properly available to resolvers

Recommended Test Plan:

1. Run cargo build to verify compilation
2. Start the GraphQL server and test entity queries with various pagination parameters
3. Test edge cases like empty results, large page sizes, and cursor navigation
4. Verify that existing GraphQL clients continue to work without changes

---

Diagram

%%{ init : { "theme" : "default" }}%%
graph TD
    subgraph "GraphQL Layer"
        A["schema.rs"]:::major-edit
        B["server.rs"]:::major-edit
        C["pagination.rs"]:::major-edit
        D["object/mod.rs"]:::minor-edit
        E["object/entity.rs"]:::major-edit
        F["Cargo.toml"]:::minor-edit
    end
    
    subgraph "Storage Layer"
        G["storage/lib.rs"]:::context
        H["proto/lib.rs"]:::context
    end
    
    subgraph "Database"
        I["sqlite/storage.rs"]:::context
    end
    
    A --> C
    B --> A
    E --> C
    C --> H
    E --> G
    G --> I
    H --> I
    
    subgraph Legend
        L1["Major Edit"]:::major-edit
        L2["Minor Edit"]:::minor-edit
        L3["Context/No Edit"]:::context
    end
    
    classDef major-edit fill:#90EE90
    classDef minor-edit fill:#87CEEB
    classDef context fill:#FFFFFF

Loading

Notes

• This PR focuses specifically on entity pagination integration. Other GraphQL object types (event_message, model, etc.) still use the old pagination system and should be updated in follow-up PRs for consistency
• The conversion between GraphQL connection arguments and proto pagination parameters maintains backward compatibility but may need fine-tuning based on testing
• Network authentication issues prevented local testing, so thorough CI verification is critical

Link to Devin run: https://app.devin.ai/sessions/b6d4ddab01ae41559c9e6efec6ac6e55
Requested by: @Larkooo

[devin-ai-integration]

Original prompt from [email protected]:

update the graphql dojoengine/torii torii/crates/graphql/src/lib.rs and all of the queries and object types etc.. to use the pagination in torii/crates/proto/src/lib.rs and the sqlite/sqlite/src/query.rs to use the query builder and execute paginated query 


You only need to look in the following repo: dojoengine/torii

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring