linksplatform / linksplatform/Data.Doublets.Gql
Nim Doublets Adapter via GraphQL client + Native DLL
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 9
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
500 RUB reward can be claimed by anyone who completes this task.
This adapter should provide standard Doublets CRUD operations API in the native to Nim code style (the most commonly used one).
The libraries' architecture should take in account the ability to swap GraphQL with a native library that will be shipped later (when we finish translation to C++).
The GraphQL client layer should be usable separately as well as native to Nim's API.
There should be 3 packages for Nimble:
1. Platform.Data.Doublets.Native (DLL api wrapped in Nim only)
2. Platform.Data.Doublets.Gql.Client (GraphQL client to doublets only)
3. Platform.Data.Doublets.Client (Abstract API for both Platform.Data.Doublets.Native and Platform.Data.Doublets.Gql.Client)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing GraphQL client and native DLL boundary, then map the proposed Nimble packages: Platform.Data.Doublets.Native, Platform.Data.Doublets.Gql.Client, and Platform.Data.Doublets.Client. Done means the three packages expose standard Doublets CRUD operations, the GraphQL client works independently, and the abstract client can use either implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, nim
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100