How to handle auth
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- graphql
- Domain
- authentication, documentation
Research direction
Review the golden path references to auth through the linked repository code search, then compare the existing GraphQL authorization page and the linked Ent privacy guidance. Clarify whether authentication belongs in the golden path and agree on the supported guidance before making a documentation change.
Written by the indexing model from the issue text.
Description
I see a few mentions of "auth" in the golden path (https://github.com/search?q=repo%3Agraphql%2Fgolden-path%20auth&type=code) but no guidelines yet on how best to implement auth.
Is this something you think the golden path should cover? Or is this scope creep (since it implies setting guidance on the rest of your architecture too).
We already have a page on this here: https://graphql.org/learn/authorization/
Which suggests 2 options:
- put auth in a logic layer
- use an @auth (or similar) directive
fwiw, imo: (1) > (2), but (2) is more popular[citation needed] because not many OSS ORM libraries have this built-in, in the same way that ent does.
Maybe the golden path can suggest that either of these are acceptable, with a preference for (1) if available.
wdyt?
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- 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
- 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.
More from graphql/golden-path
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
graphql/golden-path#5 ·
-
Add timeoutsOpen
Difficulty 5/5 Over a week Newbie friendliness 35/100
graphql/golden-path#4 ·
-
Work with OWASPOpen
Difficulty 3/5 1-2 days Newbie friendliness 35/100
graphql/golden-path#3 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
graphql/golden-path#2 ·
All issues in graphql/golden-path
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Add "append" and "prepend" slots for vue-vuetify extended renderersPossibly taken @simeyc claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
eclipsesource/jsonforms#2668 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
cobot/zapier#520 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
README の通知条件を実際の判定処理に合わせるPossibly taken @unhappychoice claimed this today. Openfactory:in-progress priority:medium
Difficulty 1/5 Under an hour Newbie friendliness 90/100
unhappychoice/oss-issue-opener#395 · 1 comment ·
Maintainers usually reply within 1 day