[Brainstorming] Survey questions

Open
  • Is something wrong?
#3 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
graphql

Research direction

Start with the linked discussion in graphql/community-wg#55 and the Discord conversation to understand the nullability tradeoff and survey context. The issue lists three questions about client, code generation, and partial data, plus optional contact information with consent; determine whether a survey is still needed and how to collect responses. Done means an agreed survey is available to gather input from affected users.

Written by the indexing model from the issue text.

Description

Opening this issue because a question came up while discussing nullability that would be great to ask in a survey and I'm writing it down before completely forgetting about it 🙃

Questions would be:

  • What client are you using?
    • urql, apollo, relay, etc...
    • no client, I use fetch() directly
  • Are you using codegen?
  • Are you handling partial data?

The intersection of fetch() + codegen + partial data could potentially be impacted by some of the semantic nullability solutions and it'd be grand to have some input to help decide on the tradeoff.

Bonus point if we can ask for contact info and reach out to those folks (with their agreement of course).

See https://github.com/graphql/community-wg/issues/55

Dominant language
No language data
Stars
1
Forks
0
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from graphql/working-sessions

All issues in graphql/working-sessions

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.