Orientação gerada a partir de informações públicas. Apenas para referência.
gql_dio_link é um link de término GraphQL para Dart que permite executar solicitações GraphQL usando o Dio, um poderoso cliente HTTP. Ele se integra perfeitamente ao ecossistema gql-dart, aproveitando os recursos robustos do Dio, como interceptadores, transformação de requisições/respostas e tratamento de erros. Projetado para comunicação eficiente baseada em JSON, suporta todas as principais plataformas, incluindo móvel, web e desktop. Ideal para aplicativos que exigem controle flexível sobre HTTP e capacidades avançadas de rede dentro de fluxos GraphQL.
Casos de uso
Integrando o GraphQL com lógica HTTP personalizada
Usando os interceptores do Dio para autenticação
Manipulação de transformações complexas de solicitação/resposta
Criando aplicativos multiplataforma com lógica de rede compartilhada
Implementando mecanismos de repetição via Dio
Personalizando cabeçalhos e tempos limite
Principais recursos
Construído sobre o Dio para controle avançado de HTTP
Suporta execução do GraphQL baseada em JSON
Oferece interceptores para middleware
Compatibilidade multiplataforma
Integração fácil com gql-dart
Manipulação de solicitação/resposta configurável
Indicado para
Desenvolvedores usando o Dio em seus projetos
Aplicativos que precisam de controle granular do HTTP
Equipes construindo clientes escaláveis de GraphQL
Projetos que exigem rede independente de plataforma
Usuários que desejam estender o comportamento do GraphQL com middleware HTTP
Considerações
Requer familiaridade com o Dio
Sobrecarga adicional de dependência
Pode ser necessário configuração manual para configurações avançadas
Não ideal para casos de uso simples de HTTP
Limitado ao transporte JSON
Dependente da estabilidade do ecossistema gql-dart
README original
Snapshot do README original do repositório-fonte vinculado. Consulte o repositório para o conteúdo mais recente.
gql-dart/gql
This is an effort to advance the Dart GraphQL ecosystem.
It consists of multiple packages and libraries centered around GraphQL AST.
Core
The core of this project is the GraphQL parser which parses GraphQL strings into an AST. The parsed AST can then be transformed, visited and printed back to GraphQL string.
To enable development of GraphQL clients, we provide type definitions used to execute GraphQL operations. They include AST-based operation, request with per operation context, and response. These types are used by the Links.
Link is the current client implementation. Link is GraphQL AST-aware request/response middleware. They can be used to build a pipeline to deduplicate requests, conditionally transform requests and responses (including the context), and eventually send the requests to the server.
The goal of this project is to expand Dart GraphQL ecosystem
and to build a community around this vendor-neutral implementation.
Community contributions are welcome.
Release Process
This repository uses Melos to manage the monorepo and handle releases. The release process is partially automated through GitHub Actions.
Repository Structure
The repository is organized into several package categories:
Core packages:
gql: Core GraphQL package
gql_tristate_value
gql_code_builder_serializers
gql_code_builder
Execution packages:
gql_exec
gql_link
Link implementations:
gql_http_link
gql_dio_link
gql_websocket_link
gql_dedupe_link
gql_error_link
gql_transform_link
Build packages:
gql_build
Local Development
To get started with local development:
Install Melos:
dart pub global activate melos && dart pub get
Bootstrap the workspace:
melos bootstrap
Run tests:
melos test
Release Process
Automated Publishing
The publish workflow is automated via GitHub Actions and triggers when:
Changes are pushed to the master or release branches AND include changes to any pubspec.yaml file
Manually triggered through GitHub Actions UI
The automated process:
Validates all packages (formatting, analysis, and tests)
Publishes packages in dependency order:
Core packages first
Execution packages second
Link implementation packages third
Build packages last
Manual Release Steps
To create a new release manually:
Ensure you're on the branch you want to release from (master or release)
Version the packages using one of the following commands:
# For a patch release
melos run bump-patch
# For a minor release
melos run bump-minor
# For a major release
melos run bump-major
# For an alpha release
melos run bump-alpha
# To graduate from prerelease(alpha) to stable
melos run graduate
Push the changes and tags:
git push && git push --tags
The GitHub Action will automatically handle publishing to pub.dev if changes include pubspec.yaml files
Versioning Rules
Use bump-patch for backward-compatible bug fixes
Use bump-minor for backward-compatible features
Use bump-major for breaking changes
Use bump-alpha for prerelease versions
Use graduate to promote prerelease versions to stable
Available Melos Commands
melos bootstrap: Set up the workspace
melos clean: Clean all packages
melos test: Run tests for all packages
melos format: Format all packages
melos analyze: Run static analysis
melos build: Run build_runner for all packages
melos publish: Publish packages to pub.dev
Troubleshooting
If the automated publish fails:
Check the GitHub Actions logs for specific errors
Ensure all tests are passing locally: melos test
Verify that version numbers in pubspec.yaml files are correct
Check that all dependencies are properly versioned
For manual publishing (if needed, requires pub dev authentication):