VFolder GraphQL Strawberry v2 Migration
- Dominant language
- Python
- Stars
- 670
- Forks
- 183
- Avg merge
- 15h 13m
- Merged PRs (30d)
- 368
Description
Migrate vfolder GraphQL API from legacy Graphene (gql_legacy/vfolder.py) to Strawberry-based v2 implementation (gql/vfolder_v2/).
Scope:
- 11 legacy types → Strawberry @gql_pydantic_type / @gql_node_type
- 9 query resolvers → @gql_root_field
- 2 mutations → @gql_mutation
- New VFolder Adapter layer (adapters/vfolder.py)
- Federation setup and legacy deprecation
Foundation already in place:
- DTOs complete in common/dto/manager/v2/vfolder/ (VFolderNode, 18 Inputs, 14 Payloads)
- Data layer exists (manager/data/vfolder/)
- Service/Processor layer exists (manager/services/vfolder/)
- Repository layer exists (manager/repositories/vfolder/)
Total: 9 SP (~2 weeks)
JIRA Issue: BA-5424
Contributor guide
Research direction
Start by comparing gql_legacy/vfolder.py with the existing gql/vfolder_v2/ implementation, then read the DTOs in common/dto/manager/v2/vfolder/ and the data, service, and repository layers named in the issue. Done means the 11 types, 9 query resolvers, 2 mutations, VFolder adapter, federation setup, and legacy deprecation are migrated within the stated scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend-api-design
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100